Malicious Code Injection in monthly_peacock-silentdev Package
Summary
MAL-2025-105963: Malicious code in monthly_peacock-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 monthly_peacock-silentdev package is part of the npm ecosystem, often utilized for various JavaScript applications. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. Its functionality is compromised, leading to significant security risks.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the monthly_peacock-silentdev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially leading to the exploitation of unsuspecting developers who may unknowingly use these compromised packages. The ramifications include loss of control over package integrity, potential data breaches, and damage to developer reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall monthly_peacock-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 remove the monthly_peacock-silentdev package from your project by executing: npm uninstall monthly_peacock-silentdev. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The monthly_peacock-silentdev package has been identified as containing malicious code that poses significant security risks. It is essential to take immediate action by updating or removing the package to protect your application and maintain the integrity of your development environment.
See every vulnerability recorded for monthly_peacock-silentdev →
FAQ
The vulnerability involves malicious code that modifies package.json files and republishes compromised packages to the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.
Risks include potential data breaches, loss of package integrity, and damage to developer reputation due to the use of compromised packages.
Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and avoid using packages from untrusted sources.
If an immediate update is not possible, consider uninstalling the package to mitigate risks until a secure version is released.
