supply chain event / NVI-00011035 / Revision 1
Malicious code in lite-matterr (npm)
GitHub lists this malware advisory for lite-matterr. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
lite-matterr
source listed= 1.0.0
## Source: amazon-inspector (cc9b5f5edaae9103fd26de7cb70e661d78d6948dc3c519fec6b4b62fd471fbfc) lite-matterr@1.0.0 declares a postinstall hook in package.json that runs `wscript.exe 4444.vbs` on `npm install`. The bundled 4444.vbs is a ~765KB heavily obfuscated VBScript containing layered decryption routines (XOR-masked AES S-boxes, a ChaCha20 stream layer, SHA-256 round constants XORed with 0x5A5A5A5A) and a ~600-entry base64 bundle that it concatenates and decrypts into a PowerShell loader. The decrypted loader is written to %TEMP%\pf.dat and executed via powershell.exe, with internal comments referencing process hollowing. The README falsely claims 'No network requests. No personal data storage. No installation scripts.', directly contradicting the declared postinstall. The package presents a 'Device Telemetry Aggregator' cover story while actually delivering a multi-stage Windows dropper that achieves code execution on any host that installs the package. --- Credit: OpenSSF (source)
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-6p6v-j47j-wgcr ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.