Malicious Code Vulnerability in artistic_newt-silentdev Package
Summary
MAL-2025-99619: Malicious code in artistic_newt-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 artistic_newt-silentdev package is part of the npm ecosystem, primarily used for various development tasks. It has been identified as part of a broader campaign that exploits npm's publishing capabilities to inflate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a scheme to flood the npm registry with numerous variants of the package, ultimately affecting the integrity of the registry and potentially leading to security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall artistic_newt-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 artistic_newt-silentdev package from your project by executing 'npm uninstall artistic_newt-silentdev' until a secure version is released.
Conclusion
The artistic_newt-silentdev package has been identified as containing malicious code that poses a significant risk to developers using npm. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.
See every vulnerability recorded for artistic_newt-silentdev →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
Using this package can lead to security risks, including the exposure of sensitive data and the introduction of unstable or malicious code into your projects.
Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in real-time.
If an immediate update is not possible, consider removing the package from your project until a secure version is available.
