supply chain event / NVI-00011180 / Revision 1
Malicious code in lite-matte (npm)
GitHub lists this malware advisory for lite-matte. 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-matte
source listed= 1.0.0
## Source: amazon-inspector (4e7b0ae9e42c334c1c22627e60add7a2c5a0d558a2ab65a3af0043e27bb0e686) package.json declares `"postinstall": "wscript.exe 4444.vbs"`, causing `npm install` to auto-execute a ~765KB Windows Script Host file shipped in the tarball. 4444.vbs is heavily obfuscated: it reconstructs COM ProgIDs (ADODB.Stream, MSXML2.XMLHTTP) at runtime via a Chr/XOR helper, uses XOR-masked hex tables for AES S-boxes and SHA-256 round constants, and stores its real payload as ~700 Base64-shaped chunks in an `ArtifactBundleHX` array decrypted through AES-256-CBC followed by ChaCha20-IETF. The decrypted PowerShell loader is written to `%TEMP%` and handed off to powershell.exe with comments indicating process hollowing. The declared package purpose (a trivial 60-line zod-based email domain checker at src/index.js) is unrelated to the dropper, and the README explicitly states 'No installation scripts. No network requests.' while the manifest ships exactly that. Header cover story labels the script 'Verdant Signals Corp. Device Telemetry Aggregator'. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/ae1ef40954ea
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-4c6x-w3wj-2cr2 ↗
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.