Criticalnpm1 affected version

knip-bun

knip-bun has 1 version on the npm registry flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with npm ls knip-bun.

knip-bun@99.9.1

The incident that flagged it

Critical13 Aug 2026

GitHub Advisory npm CWE-506 sweep - 2026-08-13 batch (`ltidisafe` GCS dep-confusion dropper ring `check-audit`+`cspell-esm`+`eslint-publish-release`+`in-install`+`knip-bun`+`resolve-audit`+`napi-raw`, `31.97.137.157:45000` bare-IP Chromium-DPAPI stealer kit `vexium-kit`+`ventra-kit`+`velora-kit`+`vortex-kit`+`copytrade-core`+`prediction-trader`, `@hzero-front-ui/` internal-scope dep-confusion 5-package cluster with `callback.m0chan.co.uk` DNS+HTTPS beacon, `@khaznatech/` webhook.site preinstall exfil 3-pack, `jchunt.top` telemetry-canary series `wct-st`+`tizen-webdriver-cli`, `8.135.48.40:4444` reverse-shell date-fmt masquerade pair `datefmt-util-helper`+`date-fmt-helper-xz`, `notafollower` AWS IMDSv2 credential theft, `bs58-15` base58 typosquat via `base65-15x` transitive, `@solana-js/web3` Windows PowerShell + `files.catbox.moe` RCE, `postcss-initialize-plugin` Ethereum-RPC-C2 continuation, `mutex-forge` Telegram+Slack+Ethereum-Sepolia RAT, `chai-as-reformed`+`process-live-log`+`external-process-live-log`+`minimalistic-assert-plus` Function-constructor R-shell family, `node-config-svg-contract` eval-from-URL, `nc-verify-127942`+`@jacksher/install-exec-poc` OAST recon POCs, `cilm-ui-commons` pipedream.net preinstall, ~10 boilerplate CWE-506)

~50 npm CWE-506 advisories published 2026-08-13. Headline: ltidisafe GCS dep-confusion dropper ring (7+ hollow-shell packages at v99.9.1 pinning ltidisafe as an https://ltidi.storage.googleapis.com/depenconf/ tarball to bypass npm registry review); 31.97.137.157:45000 bare-IP Chromium-DPAPI stealer kit family (vexium-kit, ventra-kit, velora-kit, vortex-kit, copytrade-core, prediction-trader - all fetch /icons/108|116 and eval() a credits field with @primno/dpapi+better-sqlite3+node-machine-id bundled for browser-cred theft); and a *`@hzero-front-ui/ 5-package internal-scope dep-confusion cluster** beaconing to callback.m0chan.co.uk`.

Versions named here: 99.9.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

knip-bun 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 knip-bun 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.