Which versions of knip-bun are malicious?

The following npm versions of knip-bun are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate knip-bun if I installed it?

knip-bun is a typosquat — you almost certainly intended a legitimately-named package. Remove knip-bun, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed knip-bun — how do I know if it already compromised me?

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

Is knip-bun part of a known attack campaign?

Yes — knip-bun is associated with the IN-MAL-2026-017680, GHSA-xrrj-hrq9-xvxg campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find knip-bun across my projects, lockfiles, and CI pipelines?

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

Malicious package

knip-bunnpm

knip-bun is a confirmed malicious npm package (MAL-2026-13983) that typosquats a legitimate package to trick installs (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in knip-bun (npm)

MAL-2026-13983

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall knip-bun

What this malware does

Package knip-bun typosquats the popular knip linter. The main module is an empty stub (module.exports = {}), and package.json declares a dependency ltidisafe pinned to an arbitrary Google Cloud Storage URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.8.tgz) rather than a package on the npm registry. On npm install, npm downloads and installs the tarball from that bucket into the installer's dependency tree and runs whatever install/lifecycle logic it contains. The bucket is unaffiliated with the knip or bun projects, and the fetched tarball is fully controlled by whoever owns that GCS bucket.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

3d412258df9a21f510333926a9be29bed8ae6368e549e295c84e187bdc1a3725

5aa3848c6982142717f50c64c192504c993dea3d7440d11588703cf6d5e656d9

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for knip-bun (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging knip-bun across your stack and pipelines.
If you installed it — respond
knip-bun is a typosquat — you almost certainly intended a legitimately-named package. Remove knip-bun, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If knip-bun 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.
How O3 protects you
O3 blocks knip-bun 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. knip-bun on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017680GHSA-xrrj-hrq9-xvxg

References

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database