Malicious Code Injection in fixed_louse_blue-23 Package
Summary
MAL-2025-102807: Malicious code in fixed_louse_blue-23 (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 fixed_louse_blue-23 package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability in the fixed_louse_blue-23 package stems from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these tainted packages, leading to potential exploitation and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall fixed_louse_blue-23If 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, avoid using the fixed_louse_blue-23 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.
Conclusion
The fixed_louse_blue-23 package poses a significant security risk due to its malicious code designed to manipulate npm registry behaviors. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for fixed_louse_blue-23 →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the inclusion of malicious code in your project, compromising its security and potentially affecting your reputation as a developer.
You should uninstall the fixed_louse_blue-23 package immediately and check your project for any unintended consequences caused by its use.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for any open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
