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

uncaxssnpm

Advisory published Updated

uncaxss is a confirmed malicious npm package (MAL-2026-10176) that executes malicious code on install (malicious versions 1.3.4, 1.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in uncaxss (npm)

MAL-2026-10176
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall uncaxss

What this malware does

Package ships an obfuscated dist/index.js that is invoked from the postinstall lifecycle hook (node dist/index.js). At install time, the script performs an HTTPS GET to https://onch.cc/test1.txt (and https://onch.cc/test2.txt), base64-decodes the response body, and executes it via new Function('require', decoded)(), granting the fetched code full Node.js capabilities (including require) on the installer's machine. The dropper is gated by process.env.P == 1, allowing the attacker to keep the payload dormant on incidental installers and detonate selectively (e.g., on CI runners where P is set). The fetching logic is obfuscated using javascript-obfuscator (hex identifiers, rotating string array, decoder wrapper), and the package's own build script ("obfuscate": "javascript-obfuscator./dist/index.js...") confirms obfuscation is applied deliberately before publish. The remote host onch.cc is unrelated to any documented package purpose (the package has no README), and the fetched content is opaque, mutable, and unpinned. This is a classic install-time RCE dropper with attacker-controlled remote code execution on npm install.

Malicious versions

2 flagged
1.3.41.3.5

Indicators of compromise (SHA-256)

aa3a99decf218ff512c0594cf9546d295c36215b1b573d64ba2d32c1ead49d68
acda9720ae54881219c0fbcee73795be85877d292aa62662f7cb6b92e775f608

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for uncaxss (2 malicious versions).

  2. If you installed it — respond

    Remove uncaxss 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.

  3. Did it already run?

    If uncaxss 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. uncaxss on npm has been identified as a malicious package (versions 1.3.4, 1.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009713IN-MAL-2026-009712

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks uncaxss-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.

Explore

uncaxss (npm) malicious package — MAL-2026-10176 | O3 Security