Malicious Code Injection in snipe_sapphire-61: A Threat to npm Packages
Summary
MAL-2025-98368: Malicious code in snipe_sapphire-61 (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
snipe_sapphire-61 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, allowing developers to publish and manage their packages. However, it has been compromised, leading to significant security concerns due to its malicious behavior.
Vulnerability Detail
The vulnerability in snipe_sapphire-61 originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file, removing private flags and changing version numbers. This behavior can lead to the proliferation of untrusted packages, potentially compromising the integrity of the npm ecosystem and affecting developers' reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall snipe_sapphire-61If 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 prevent the installation of the compromised package by using the following command to uninstall it: npm uninstall snipe_sapphire-61. Additionally, you can monitor your project for any unauthorized changes to package.json.
Conclusion
The snipe_sapphire-61 package has been identified as containing malicious code that poses a significant threat to the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for snipe_sapphire-61 →
FAQ
The malicious code modifies package.json to remove private flags and changes version numbers, allowing for the automatic generation and publication of derivative packages.
You can use Vulert, which monitors open-source vulnerabilities in real-time. By uploading your package-lock.json file, you can receive alerts about any vulnerabilities, including this one.
Using the compromised package can lead to the pollution of the npm registry, unauthorized changes to your project, and potential security risks for your application.
Regularly updating your dependencies, using tools like Vulert to monitor vulnerabilities, and auditing your packages can help prevent similar issues.
If you cannot update the package, consider removing it from your project and replacing it with a safer alternative.
