Malicious Code Injection in bright_wombat-silentdev Package
Summary
MAL-2025-100111: Malicious code in bright_wombat-silentdev (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The bright_wombat-silentdev package is part of the npm ecosystem, commonly used for various JavaScript applications. It is often utilized for its functionalities in token reward campaigns. However, this package has been identified as part of a malicious scheme that floods the npm registry with derivative packages, impacting developers' reputation scores and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the bright_wombat-silentdev package originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The scripts continuously republish these variants, polluting the npm registry and potentially compromising the security of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bright_wombat-silentdevIf 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
As a temporary workaround, you can avoid using the bright_wombat-silentdev package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and integrity of the packages you choose to include in your project.
Conclusion
The bright_wombat-silentdev package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for bright_wombat-silentdev →
FAQ
It is an npm package associated with token reward campaigns, but it has been identified as malicious.
The vulnerability can lead to the injection of malicious code, compromising your application's security and integrity.
You should uninstall the package immediately and look for alternative solutions.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without signing up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
