Malicious Code Injection in united_shark-silentdev: A Threat to npm Users
Summary
MAL-2025-110140: Malicious code in united_shark-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 package 'united_shark-silentdev' is part of a larger ecosystem within npm, primarily associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, 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 'united_shark-silentdev' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior not only affects the reputation of developers but also poses a risk of dependency confusion and potential exploitation by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall united_shark-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 avoid using the 'united_shark-silentdev' package altogether. If it is a dependency of another package, consider replacing it with a safer alternative or contacting the maintainer of the parent package for guidance on removing the dependency.
Conclusion
The 'united_shark-silentdev' package poses a significant risk due to its malicious behavior, which can compromise the integrity of your projects. It is crucial to take immediate action by uninstalling the package and monitoring your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for united_shark-silentdev →
FAQ
The package contains malicious code that modifies package.json files and republish variants to pollute the npm registry.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected.
You should uninstall the package immediately using 'npm uninstall united_shark-silentdev' and check for any other affected dependencies.
While specific alternatives may vary based on your project's needs, consider researching trusted packages that provide similar functionality without the associated risks.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.
