Which versions of pixelblm are malicious?

The following npm versions of pixelblm are flagged malicious: 10.29.5. Treat any of these as compromised.

How do I remediate pixelblm if I installed it?

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

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

Yes — pixelblm is associated with the GHSA-vmr5-frwv-4v29, RLMA-2025-05917, RLUA-2025-06449 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 pixelblm 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 pixelblm (version 10.29.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pixelblm across your stack and pipelines.

Malicious package

pixelblmnpm

pixelblm is a confirmed malicious npm package (MAL-2025-49263) that executes malicious code on install (malicious version 10.29.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pixelblm (npm)

MAL-2025-49263

Immediate action

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

npm uninstall pixelblm

What this malware does

The package pixelblm 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.

Malicious versions

1 flagged

10.29.5

Indicators of compromise (SHA-256)

2ee65b21f5be8ce779e9dcc8e25883cf38d8856e9c2938e1e9949ad4ea50c111

3d62ab0b93a24a50d76861d245aca1b9d067170b8dc681e470fa1c003f2eed10

994405bd205b30a5c5e160c7878f400fe03a57cfa66871896a35676dd8151d67

7c0c69237b210726d9bb8ceb24a55053745597c6115b24bab9bb4c7f62b3a30e

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pixelblm (version 10.29.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pixelblm across your stack and pipelines.
If you installed it — respond
Remove pixelblm 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 pixelblm 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 pixelblm 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. pixelblm on npm has been identified as a malicious package (version 10.29.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vmr5-frwv-4v29RLMA-2025-05917RLUA-2025-06449

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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