Malicious Code Detected in sinta-sasag67-breki: A Threat to npm Users
Summary
MAL-2025-75459: Malicious code in sinta-sasag67-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 'sinta-sasag67-breki' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files, such as package.json, and republish variants to the npm registry, thereby polluting it.
Vulnerability Detail
The vulnerability in 'sinta-sasag67-breki' originates from its involvement in a scheme to manipulate the npm registry. The package contains scripts that remove private flags from package.json, alter version numbers, and generate random package names, which can lead to the proliferation of malicious or low-quality packages. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sinta-sasag67-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 package by not including it in your project dependencies. If you have already installed it, ensure to remove it as mentioned above. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The 'sinta-sasag67-breki' package presents a significant risk to npm users due to its malicious nature and ability to manipulate package files. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities. Staying vigilant and proactive in managing your dependencies will help safeguard your applications.
See every vulnerability recorded for sinta-sasag67-breki →
FAQ
The primary threat is the modification of package.json files and the creation of numerous malicious packages that can compromise the integrity of the npm registry.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed the package, you should immediately uninstall it using 'npm uninstall sinta-sasag67-breki' and check your project for any other affected dependencies.
Yes, tools like Vulert can monitor your package-lock.json for open-source vulnerabilities in real-time, helping you stay informed about potential threats.
Regularly update your dependencies, use trusted sources for packages, and employ monitoring tools like Vulert to keep track of vulnerabilities.
