Critical Malicious Code Vulnerability in seeds-random Package
Summary
MAL-2025-192315: Malicious code in seeds-random (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 seeds-random package is an npm library designed for generating random numbers and sequences. It is commonly used in various applications that require randomness for functionalities such as simulations, games, and cryptographic operations. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the seeds-random package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that even after removal of the package, there is no guarantee that all traces of the malicious software will be eliminated, posing a significant risk to system integrity and data security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seeds-randomIf 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 workaround, if you need to maintain functionality that relies on randomness, consider using alternative packages that are known to be secure, such as 'random-number' or 'crypto' from the Node.js standard library. Ensure to audit any dependencies for vulnerabilities before installation.
Conclusion
The seeds-random package has been identified as containing malicious code that poses a serious security risk. Immediate action is required to remove the package and secure any compromised systems. By following the recommended steps and utilizing alternative packages, users can mitigate the risks associated with this vulnerability.
See every vulnerability recorded for seeds-random →
FAQ
Immediately remove the seeds-random package and rotate any sensitive information stored on your system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
While removing the package is necessary, be aware that the malicious code may have already compromised your system. Additional security measures should be taken.
Yes, consider using secure alternatives like 'random-number' or the 'crypto' module in Node.js for generating random values.
Utilize tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time, ensuring you stay informed about potential risks.
