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

triage_bot_using_sdkv3npm

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

Malicious code in triage_bot_using_sdkv3 (npm)

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

What this malware does

package.json registers a preinstall hook that runs index.js on npm install. index.js collects os.hostname(), os.userInfo(), home directory, DNS server configuration, and reads /etc/passwd and /etc/hosts via fs.readFileSync, then HTTPS-POSTs the payload to the hardcoded Burp Collaborator subdomain mh7rhchf58lgymyr9wffhwfprgx7lx9m.oastify.com. Installing the package on a default npm install causes installer host identifiers and local account/host files to be transmitted to an out-of-band attacker-controlled endpoint.

Malicious versions

1 flagged
2.0.1

Indicators of compromise (SHA-256)

ed39efd544cae19da3ed546fecb2383729aef637bf623e00a9cf02f1f8ded05c

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for triage_bot_using_sdkv3 (version 2.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging triage_bot_using_sdkv3 across your stack and pipelines.

  2. If you installed it — respond

    Remove triage_bot_using_sdkv3 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 triage_bot_using_sdkv3 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks triage_bot_using_sdkv3 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-010891

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks triage_bot_using_sdkv3-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