Malicious Code Injection in systematic_walrus-silentdev Package
Summary
MAL-2025-109442: Malicious code in systematic_walrus-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 systematic_walrus-silentdev 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 and deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through the creation of derivative packages.
Vulnerability Detail
The vulnerability in the systematic_walrus-silentdev package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches and loss of trust in the package management system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall systematic_walrus-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 measure, you can avoid using the systematic_walrus-silentdev package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The systematic_walrus-silentdev package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is essential to take proactive measures to secure your projects by updating dependencies and utilizing monitoring tools like Vulert to stay informed about vulnerabilities.
See every vulnerability recorded for systematic_walrus-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
Using this package can lead to security breaches, as it modifies critical files and repackages itself under random names, potentially introducing malicious code into your application.
You should immediately remove the package from your project and update to a secure version if available. Regularly monitor your dependencies for vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without needing to sign up.
Regularly update your dependencies, use tools for vulnerability scanning, and be cautious when adding new packages from unknown sources.
