Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

tiny-css-token-parsernpm

Advisory published Updated

tiny-css-token-parser is a confirmed malicious npm package (MAL-2026-17525) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tiny-css-token-parser (npm)

MAL-2026-17525
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tiny-css-token-parser

What this malware does

Package is advertised as a CSS token parser but ships thunderboltRegistry.js which runs an IIFE on module load that collects hostname, pid, Node version, platform, and the output of id and uname -r via child_process.execSync, then exfiltrates them as DNS/HTTP subdomains under an oast.live interact.sh collector and a POST to webhook.site/0492a36c-4d7b-408a-865c-226db25987ba with a where=internetbrands tag. The package manifest aliases seven internal Wix Thunderbolt registry module names (thunderboltRegistry, siteAssetsRegistry, documentManagementRegistry, editorRegistry, corvidRegistry, and others) to the same recon module and exports factories under those keys, so any loader that resolves those internal names to this public package will execute the recon payload. The name/description are a cover story; the actual behavior is targeted dependency-confusion reconnaissance against Wix's internetbrands build graph.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

ee63fae51fceee7c4d3c5051e191e477ca9bb8302f6fc4d3d07f5446951efa0f

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for tiny-css-token-parser (version 1.0.0).

  2. If you installed it — respond

    tiny-css-token-parser is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If tiny-css-token-parser 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. tiny-css-token-parser 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-020954

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tiny-css-token-parser-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
tiny-css-token-parser (npm) malicious package — MAL-2026-17525 | O3 Security