Malicious Code Injection in vera-soto9-breki: A Threat to npm Users
Summary
MAL-2025-75997: Malicious code in vera-soto9-breki (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 package 'vera-soto9-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of such packages is to manipulate npm's publishing system to inflate developer reputation scores, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'vera-soto9-breki' originates from its design to include malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include the pollution of the npm registry, potential exposure of sensitive data, and a compromised development environment for users relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vera-soto9-brekiIf 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, users can remove the 'vera-soto9-breki' package from their project by executing 'npm uninstall vera-soto9-breki'. This will prevent the execution of any malicious code associated with the package until a secure version is available.
Conclusion
The 'vera-soto9-breki' package poses a significant threat due to its malicious code that manipulates npm's publishing system. Users are advised to take immediate action by updating or uninstalling the package and utilizing tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for vera-soto9-breki →
FAQ
The main issue is that it contains malicious code designed to manipulate npm's publishing system, which can lead to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
The risks include exposure to malicious code, compromised developer reputation, and potential data leaks due to the package's behavior.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
Immediately uninstall the package and review your project for any potential impacts. Consider using alternative packages that are known to be secure.
