Malicious Code Detected in pixel-bloom Package - Security Alert

pixel-bloom Updated 02 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191580: Malicious code in pixel-bloom (npm). Affects pixel-bloom versions 10.29.1 – 10.29.4. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The pixel-bloom package is a popular npm library used for creating vibrant and dynamic visual effects in web applications. It provides developers with tools to enhance user interfaces through colorful animations and graphics. However, recent findings have revealed that certain versions of this package contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the pixel-bloom package stems from the introduction of malicious code in versions 10.29.1 and 10.29.4. This code can potentially compromise the security of applications by allowing unauthorized access or manipulation of data. The malicious code was identified by ReversingLabs, which has documented its findings. Users of the affected versions are at risk of data breaches and other security incidents due to this vulnerability.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall pixel-bloom

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If immediate updating is not feasible, consider removing the pixel-bloom package from your project until a secure version is confirmed. You can do this by executing: npm uninstall pixel-bloom. This will prevent any potential exploitation of the vulnerability while you assess your options.

Conclusion

The discovery of malicious code in the pixel-bloom package highlights the importance of maintaining up-to-date dependencies and monitoring for vulnerabilities. By updating to the latest version and utilizing tools like Vulert, developers can safeguard their applications against potential threats.

See every vulnerability recorded for pixel-bloom →

Share this vulnerability

FAQ

The pixel-bloom package is an npm library designed for creating colorful animations and visual effects in web applications.

Versions 10.29.1 and 10.29.4 of the pixel-bloom package contain the malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without requiring any signup.

Using the affected versions can lead to unauthorized access, data manipulation, and other security breaches in your application.

Regularly update your dependencies and monitor for vulnerabilities using tools like Vulert to maintain the security of your application.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall pixel-bloom

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback