Which versions of bootstrap-utils are malicious?

The following npm versions of bootstrap-utils are flagged malicious: 4.5.0. Treat any of these as compromised.

How do I remediate bootstrap-utils if I installed it?

bootstrap-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed bootstrap-utils — how do I know if it already compromised me?

If bootstrap-utils 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 bootstrap-utils part of a known attack campaign?

Yes — bootstrap-utils is associated with the GHSA-jgjc-8w9g-8wmq, IN-MAL-2026-008615 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 bootstrap-utils 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 bootstrap-utils (version 4.5.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bootstrap-utils across your stack and pipelines.

Malicious package

bootstrap-utilsnpm

bootstrap-utils is a confirmed malicious npm package (MAL-2026-6807) that steals credentials and exfiltrates sensitive data (malicious version 4.5.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bootstrap-utils (npm)

MAL-2026-6807

Immediate action

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

npm uninstall bootstrap-utils

What this malware does

The package's index.js is heavily obfuscated with classic string-array shuffling patterns (e.g., while(!![]) loops with repeated 'shift' calls and hex-encoded indices on a single line). Obfuscation of this shape is uncommon in legitimate library code and frequently used to hide install/runtime behavior, but no concrete installer-harm behavior (exfiltration endpoint, credential read, dropper, lifecycle hook) has been corroborated in this record. The package name 'bootstrap-utils' also has confusion potential with the popular 'bootstrap' ecosystem. A human reviewer should de-obfuscate index.js to confirm intent before this version is trusted.

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

4.5.0

Indicators of compromise (SHA-256)

d3b42bbdadaf453f0ae5f3be0f2455ec5c57217e988927fd501ff6320a361ee9

d9ac4913fc1ffcabe1ed6637abc6d532abc014683f48b341ece6127a51da15d8

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bootstrap-utils (version 4.5.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bootstrap-utils across your stack and pipelines.
If you installed it — respond
bootstrap-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bootstrap-utils 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 bootstrap-utils 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. bootstrap-utils on npm has been identified as a malicious package (version 4.5.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jgjc-8w9g-8wmqIN-MAL-2026-008615

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bootstrap-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database