NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

uploader-frontendnpm

Advisory published Updated

uploader-frontend is a confirmed malicious npm package (MAL-2026-12491) that steals credentials and exfiltrates sensitive data (malicious version 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in uploader-frontend (npm)

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

What this malware does

The package's scripts.install runs node index.js, which loads ./lib/core and, on npm install, collects the installer's OS username (via os.userInfo().username), hostname (os.hostname()), and current working directory basename, encodes them as a subdomain, and issues a dns.resolve4 lookup against the hardcoded attacker domain oob.sl4x0.xyz — a DNS out-of-band beacon that exfiltrates installer identity. The require targets (dns, os, process), the API names (userInfo, username, hostname, cwd, resolve4), and the destination domain are reconstructed at runtime from String.fromCharCode numeric arrays to hide the destination and the APIs used. Package name and README advertise uploader-frontend / enterprise utilities and validation, but the auto-executed code implements no such functionality — only the beacon. The author email [email protected] shares the domain of the exfil host, and homepage points at an unrelated project (github.com/slaxorg/nms-dashboard-js), indicating publisher-controlled attacker infrastructure.

Malicious versions

1 flagged
9.9.11

Indicators of compromise (SHA-256)

434cb8e84402c02f52788e51215db45b8c7f2f229d56c51d8302993b782cf911

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for uploader-frontend (version 9.9.11).

  2. If you installed it — respond

    uploader-frontend 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 uploader-frontend 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. uploader-frontend on npm has been identified as a malicious package (version 9.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014884

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

uploader-frontend (npm) malicious package — MAL-2026-12491 | O3 Security