Malicious Code Injection in samehadaku-tss-sur7 Package
Summary
MAL-2025-165739: Malicious code in samehadaku-tss-sur7 (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 samehadaku-tss-sur7 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability in the samehadaku-tss-sur7 package originates from its association with a malicious token reward campaign. This package contains scripts designed to automatically generate and publish derivative packages with randomized names, thereby inflating developer reputation scores. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to pollution of the npm registry and potential security risks for users who inadvertently install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall samehadaku-tss-sur7If 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 measure, you can avoid using the samehadaku-tss-sur7 package and replace it with a trusted alternative. Regularly audit your package dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The samehadaku-tss-sur7 package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package from their projects and to remain vigilant about the packages they use. Regular audits and monitoring can help mitigate the risks associated with open-source vulnerabilities.
See every vulnerability recorded for samehadaku-tss-sur7 →
FAQ
The samehadaku-tss-sur7 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
If your application uses the samehadaku-tss-sur7 package, it may inadvertently install malicious code that can compromise security, lead to data breaches, or affect application performance.
You should uninstall the samehadaku-tss-sur7 package immediately and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check if your application is affected by visiting the Vulert playground.
Yes, tools like npm audit and Vulert can help you manage your dependencies and alert you to any known vulnerabilities in your packages.
