Malicious Code Injection in camilabarbosa: npm Package Vulnerability
Summary
MAL-2025-170997: Malicious code in camilabarbosa (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
Background
The camilabarbosa package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the camilabarbosa package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, primarily themed around Indonesian culture. The malicious scripts (auto.js, autopublish.js, etc.) continuously republish these variants, leading to pollution of the npm registry and potential security risks for developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall camilabarbosaIf 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 camilabarbosa package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify any vulnerabilities.
Conclusion
The camilabarbosa package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be vigilant, remove this package from their projects, and utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for camilabarbosa →
FAQ
The camilabarbosa package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code can modify your package.json file, remove private flags, and republish variants, potentially compromising your project's integrity.
You should uninstall the camilabarbosa package immediately using 'npm uninstall camilabarbosa' to mitigate any risks.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
