Which versions of blob-to-base64 are malicious?

The following npm versions of blob-to-base64 are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate blob-to-base64 if I installed it?

blob-to-base64 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 blob-to-base64 — how do I know if it already compromised me?

If blob-to-base64 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 blob-to-base64 part of a known attack campaign?

Yes — blob-to-base64 is associated with the GHSA-8m38-v5g6-whxx 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 blob-to-base64 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 blob-to-base64 (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging blob-to-base64 across your stack and pipelines.

Malicious package

blob-to-base64npm

Malicious code in blob-to-base64 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191077

Immediate action

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

npm uninstall blob-to-base64

What this malware does

The package blob-to-base64 was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

200b8ce0ee413e9267ce3a929dfcf4f072860e143f01046f3361d247b9a9b6fa

f2fafe35a1d406a9c5cedcdef426c35c207238b5b06b5da4cd4f6215a2cffe54

c5c6f8ab4b22e2ba28bac2f82c7c9d577974aafda6f190626178907579e5a474

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 blob-to-base64 (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging blob-to-base64 across your stack and pipelines.
If you installed it — respond
blob-to-base64 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 blob-to-base64 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 blob-to-base64 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. blob-to-base64 on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8m38-v5g6-whxx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks blob-to-base64-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