Malicious Code Injection in npm Package: vina-sasag72-breki
Summary
MAL-2025-76092: Malicious code in vina-sasag72-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 'vina-sasag72-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies its own package.json file.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random names for new packages. This behavior can lead to pollution of the npm registry and potential exploitation by attackers who may leverage these packages for further malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vina-sasag72-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, you can avoid using this package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The 'vina-sasag72-breki' package is compromised with malicious code that can lead to significant risks for developers and users. It is crucial to remove this package and monitor your dependencies for any signs of exploitation. Utilizing tools like Vulert can help maintain the security of your open-source projects.
See every vulnerability recorded for vina-sasag72-breki →
FAQ
The impact includes potential pollution of the npm registry and the risk of malicious exploitation through modified packages.
You can check your package.json and package-lock.json files for the presence of 'vina-sasag72-breki'.
You should remove the package immediately and monitor your project for any unusual behavior.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.
Yes, you can report vulnerabilities to npm to help improve the security of the ecosystem.
