Which versions of pixel-bloom are malicious?

The following npm versions of pixel-bloom are flagged malicious: 10.29.1, 10.29.4, 10.29.11. Treat any of these as compromised.

How do I remediate pixel-bloom if I installed it?

Remove pixel-bloom 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 pixel-bloom — how do I know if it already compromised me?

If pixel-bloom 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.

Is pixel-bloom part of a known attack campaign?

Yes — pixel-bloom is associated with the RLMA-2025-05916, RLUA-2025-06448, RLUA-2026-01490 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 pixel-bloom across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pixel-bloom (3 malicious versions).

Malicious package

pixel-bloomnpm

Advisory published Dec 1, 2025Updated Mar 19, 2026

pixel-bloom is a confirmed malicious npm package (MAL-2025-191580) that executes malicious code on install (malicious versions 10.29.1, 10.29.4, 10.29.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pixel-bloom (npm)

MAL-2025-191580

Immediate action

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

npm uninstall pixel-bloom

What this malware does

The package pixel-bloom was found to contain malicious code.

Malicious versions

3 flagged

10.29.110.29.410.29.11

Indicators of compromise (SHA-256)

1ef68d5fe34aab21507afea329ab73d555ffd6916efac668aa1ae3f9eae0388b

3e8b2781d37ee1adef96e13bb9b91bbf543cf9536031d1b42f574ffc860b8922

05f6a3130f89ce07e1cffe4fd6bd039d8135145e7f68ef05397dbf943c1c59f5

941e0531ccf4691a9e6a73d92e389139cd99de2973a821dd54acb2da9c91e846

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pixel-bloom (3 malicious versions).
If you installed it — respond
Remove pixel-bloom 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 pixel-bloom 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. pixel-bloom on npm has been identified as a malicious package (versions 10.29.1, 10.29.4, 10.29.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05916RLUA-2025-06448RLUA-2026-01490

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks pixel-bloom-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