At least one advisory flags my-ctf-helper-script-9921 on the npm registry as malicious in every release, so the releases other advisories named are not the whole story. There is no version to upgrade to: remove it outright. It is named in 2 incidents we track. my-ctf-helper-script-9921 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.
No release of this package is known good. If it is in your tree, treat the machine as compromised, not just out of date.
Version data comes from the public advisories cited on each incident page.
Check what you actually have installed with npm ls my-ctf-helper-script-9921.
The source advisories flagged the package itself rather than particular releases. Treat any resolved version as malicious and remove the dependency; there is nothing to upgrade to.
GHSA 2026-09-30 (late) + 2026-10-01: 26 new advisories (24 npm + 2 pip). Confirmed payloads: pip beautifytext import-time RAT; pip friendly-greeting-tools Snowflake credential theft to s3://pkusinski-external/; npm noverojs Baileys silent-WhatsApp-follow family continuation. Remainder are dep-confusion scope probes (Epic Games Store, mms-*) and CWE-506 boilerplate.
GHSA 2026-09-21 (late) + 2026-09-22: ~25 new npm advisories + 2 pip. Day 5 of the oob.algamil7x.xyz DNS-OOB operator adds @baanx/abis and @baanx/blockchain-config at 9.9.11. Three hardhat-* typosquats (Ethereum toolchain) carry real axios-loader RCE via ipcheck-hashed.vercel.app. @uh-platform/* (5 pkgs) plus @uol-afiliados and @asdfaskdjfksadhfkasf fire Burp Collaborator OOB. pip pullgetsage archives Telegram Desktop tdata and POSTs to Cloudflare Workers.
Treat the machine as compromisedUpgrading is not enough. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.
If my-ctf-helper-script-9921 is in your tree, these are worth checking too. They were published by the same campaign.
Version data comes from the public advisories cited on each incident page. We list only versions those advisories name and do not infer additional ones. Think this is wrong or incomplete? Tell us.
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.
A small amount of analytics helps us understand how the scanner gets used so we can make it better. Your lockfile scanning still runs entirely in your browser. We never sell or share your data. See our Privacy Policy for details.
You can change your choice later by clearing site data for dependencywatch.io.