Malicious Code Injection in samehadaku-ssi-ur7: A Threat to npm Packages
Summary
MAL-2025-165737: Malicious code in samehadaku-ssi-ur7 (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 'samehadaku-ssi-ur7' 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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'samehadaku-ssi-ur7' stems from its inclusion in a campaign that generates and publishes derivative packages with randomized names. The malicious code modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. This can result in compromised applications that unknowingly depend on these malicious packages, potentially exposing sensitive data and undermining application security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall samehadaku-ssi-ur7If 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 'samehadaku-ssi-ur7' package from your project by executing the command: 'npm uninstall samehadaku-ssi-ur7'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'samehadaku-ssi-ur7' package poses a significant security risk due to its malicious code that alters package metadata and repackages it under random names. Users are advised to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.
See every vulnerability recorded for samehadaku-ssi-ur7 →
FAQ
The vulnerability involves malicious code that modifies package metadata and repackages it under random names, leading to potential security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. Visit the Vulert playground at Vulert Scanner to check for vulnerabilities without signing up.
Using compromised packages can lead to data breaches, unauthorized access to sensitive information, and overall application instability.
Regularly updating packages, using tools like Vulert for monitoring, and auditing dependencies can help mitigate the risk of vulnerabilities.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to avoid executing any malicious code.
