Which versions of bitsight are malicious?

The following npm versions of bitsight are flagged malicious: 1.0.9, 1.1.1. Treat any of these as compromised.

How do I remediate bitsight if I installed it?

Remove bitsight 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.

I already installed bitsight — how do I know if it already compromised me?

If bitsight was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find bitsight across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bitsight (2 malicious versions).

Malicious package

bitsightnpm

Advisory published Nov 13, 2025Updated Nov 13, 2025

bitsight is a confirmed malicious npm package (MAL-2025-190490) that executes malicious code on install (malicious versions 1.0.9, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bitsight (npm)

MAL-2025-190490

Immediate action

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

npm uninstall bitsight

What this malware does

The package bitsight was found to contain malicious code.

Malicious versions

2 flagged

1.0.91.1.1

Indicators of compromise (SHA-256)

ee657cb65d10490f2b29546c27133e3049eab717c2b57bda3029643665e32899

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bitsight (2 malicious versions).
If you installed it — respond
Remove bitsight 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.
Did it already run?
If bitsight was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bitsight on npm has been identified as a malicious package (versions 1.0.9, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

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