Malicious Code Injection in romantic_mink-silentdev Package
Summary
MAL-2025-108194: Malicious code in romantic_mink-silentdev (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 'romantic_mink-silentdev' package 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 this package is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the 'romantic_mink-silentdev' package stems from its association with a malicious campaign that employs scripts to automatically generate and publish derivative packages. These scripts, named auto.js, autopublish.js, and others, modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry with potentially harmful packages, leading to security risks for users who may inadvertently install these variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall romantic_mink-silentdevIf 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 remove the 'romantic_mink-silentdev' package from your project by executing the command: 'npm uninstall romantic_mink-silentdev'. This will prevent any malicious code from executing until a safe version is available.
Conclusion
The 'romantic_mink-silentdev' package poses a significant security risk due to its malicious code that modifies package metadata and publishes harmful variants. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for romantic_mink-silentdev →
FAQ
It is an npm package associated with a token reward campaign that has been compromised to include malicious scripts.
If your application uses this package, it may inadvertently publish malicious variants to the npm registry, compromising your project's integrity.
You should uninstall the package immediately and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
