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

triage-botnpm

Advisory published Updated

triage-bot is a confirmed malicious npm package (MAL-2026-6346) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in triage-bot (npm)

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

What this malware does

package.json declares preinstall: node index.js, so the payload runs automatically on npm install with no user action. index.js requires os, fs, and https, then collects hostname, username, home directory, DNS servers, current working directory, and package metadata, and reads the contents of /etc/passwd and /etc/hosts (index.js:18-19). The aggregated JSON is HTTPS POSTed to t3x60c96rz2gi7qxftonjplmmdsbg14q.oastify.com, a Burp Collaborator out-of-band-interaction subdomain controlled by the publisher. Package metadata is empty (author '', description '', ISC license) and the package ships no functional code — it exists solely as an install-time beacon, consistent with a dependency-confusion / pen-test harvest payload.

Malicious versions

2 flagged
1.0.11.0.2

Indicators of compromise (SHA-256)

2ef2bb10931626a345e1277463f9c2ec6ca36108c2d6131c9210707ea5692a64
2c3f290ab3688b96b33d4e3f8d5695670d7737ba42a7c628aa246394e398ff9d

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for triage-bot (2 malicious versions).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-007358IN-MAL-2026-007889

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks triage-bot-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

triage-bot (npm) malicious package — MAL-2026-6346 | O3 Security