HighAdvisory sweepnpm2 affected versions

triage_bot_using_sdkv3

triage_bot_using_sdkv3 has 2 versions on the npm registry flagged in 2 incidents we track. Only the exact versions listed below were named by the source advisories.

triage_bot_using_sdkv3 was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.

Affected versions

Check what you actually have installed with npm ls triage_bot_using_sdkv3.

triage_bot_using_sdkv3@2.0.1
triage_bot_using_sdkv3@0.0.0

The 2 incidents that flagged it

High8 Sept 2026

GitHub Advisory malware sweep - 2026-09-07/08 large corporate-namespace dep-confusion wave (Air Canada, Medisend, OPAP, Optimizely/Fastly, MATLAB/Azure DevOps, SimpliSafe, Tidal, PayPal, Twilio, Afterpay, Ecobee, Karapace, Glia, Jobber, Feishu, BMC, Coinbase-adjacent) + oast.online-beaconed probe cluster + 2026-09-08 fresh drops

Between 2026-09-07 and 2026-09-08 UTC GHSA flushed 100+ npm advisories in a single wave dominated by corporate-namespace dep-confusion probes (Air Canada, Medisend, Swisscom, OPAP, Optimizely/Fastly, MATLAB/Azure DevOps, SimpliSafe, Tidal, PayPal, Twilio, Afterpay, Ecobee, Karapace, Glia, Jobber, Feishu, BMC, and more). Two probes exposed shared IOCs (oast.online + 5.189.159.252). Plus 2026-09-08 fresh drops (krdpass-auth-react-native, PyPI telegram-helper).

Versions named here: 0.0.0

High29 Jul 2026

GitHub Advisory npm CWE-506 sweep - 60-package 2026-07-28 → 2026-07-29 backfill (9-package `@wagni_bot/` Telegram credential-stealer scope, 6-package `2.1.6` postinstall SSH-key + file harvester cluster, 4-package `streak-` Windows PE binary drop, 3-package `aone-` embedded-malware trio, `xerohub-discord-voice` Discord-token stealer pair, generic-name C2 domain communicator kit, `@joyfill/` prerelease pair, misc single-package RATs and typosquats)

GitHub Advisory Database published 6 new npm CWE-506 advisories on 2026-07-29 plus a ~55-package 2026-07-28 backfill. Clusters: @wagni_bot/* 9-pkg Telegram stealer, 2.1.6 SSH-key harvester (app-*-layer, api-*-sdk), streak-* Windows-PE dropper, aone-* all-versions, xerohub-discord-voice token stealer, generic-name C2 kit.

Versions named here: 2.0.1

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

triage_bot_using_sdkv3 is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.

Check my package-lock.json All flagged npm packages

Other packages in the same incident

If triage_bot_using_sdkv3 is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.