Malicious Code Injection in ok_seahorse-silentdev Package
Summary
MAL-2025-106616: Malicious code in ok_seahorse-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The ok_seahorse-silentdev package is part of the npm ecosystem, which is widely used for JavaScript development. It is designed to facilitate various development tasks but has been compromised. This package is associated with a token reward campaign that has led to the proliferation of malicious packages on npm, affecting developers and their projects.
Vulnerability Detail
The vulnerability in the ok_seahorse-silentdev package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores and pollute the npm registry with derivative packages. The malicious code can lead to unauthorized access, data leakage, and potential exploitation of dependent applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ok_seahorse-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 ok_seahorse-silentdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes in the package.json file.
Conclusion
The ok_seahorse-silentdev package has been identified as a vector for malicious code injection, posing significant risks to developers and their projects. It is essential to remove this package and monitor your applications for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your open-source dependencies.
See every vulnerability recorded for ok_seahorse-silentdev →
FAQ
The ok_seahorse-silentdev package is an npm package used in JavaScript development, but it has been compromised to include malicious code.
The malicious code modifies your package.json file, potentially leading to unauthorized access and data leakage, as well as polluting the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any installation.
If you have installed the ok_seahorse-silentdev package, you should uninstall it immediately using 'npm uninstall ok_seahorse-silentdev' and check for any unauthorized changes in your project.
Yes, you should look for alternative packages that provide similar functionality without the associated risks. Always review the package's reputation and security before installation.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
