Which versions of lite-matterr are malicious?

The following npm versions of lite-matterr are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate lite-matterr if I installed it?

Remove lite-matterr from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed lite-matterr — how do I know if it already compromised me?

If lite-matterr was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is lite-matterr part of a known attack campaign?

Yes — lite-matterr is associated with the IN-MAL-2026-020967 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find lite-matterr across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lite-matterr (version 1.0.0).

Malicious package

lite-matterrnpm

Advisory published Oct 4, 2026Updated Oct 4, 2026

lite-matterr is a confirmed malicious npm package (MAL-2026-17513) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lite-matterr (npm)

MAL-2026-17513

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall lite-matterr

What this malware does

[email protected] 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<rand>.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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

cc9b5f5edaae9103fd26de7cb70e661d78d6948dc3c519fec6b4b62fd471fbfc

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lite-matterr (version 1.0.0).
If you installed it — respond
Remove lite-matterr from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If lite-matterr was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. lite-matterr on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020967

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks lite-matterr-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database