Malicious Code Injection in tania-sate30-breki: A Threat to npm Packages
Summary
MAL-2025-75601: Malicious code in tania-sate30-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 tania-sate30-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 compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tania-sate30-breki originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other packages and developers. The malicious scripts included (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult to track and mitigate the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tania-sate30-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 the tania-sate30-breki package and monitor your project for any dependencies that may inadvertently include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The tania-sate30-breki package poses a significant risk due to its malicious code that modifies package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for tania-sate30-breki →
FAQ
The impact includes potential pollution of the npm registry, which can affect the integrity of other packages and lead to security risks for developers using those packages.
You can use Vulert to check your package-lock.json for vulnerabilities without requiring access to the code or installation. Visit the Vulert playground at Vulert Scanner.
You should remove the package immediately and monitor your project for any dependencies that may have been affected.
Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software.
Regularly audit your dependencies, use tools for vulnerability scanning, and stay updated with the latest security patches for your packages.
