Malicious Code Injection in enormous_emu-silentdev: A Threat to npm Users
Summary
MAL-2025-102102: Malicious code in enormous_emu-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 package 'enormous_emu-silentdev' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to users who may unknowingly install these malicious packages.
Vulnerability Detail
The vulnerability in 'enormous_emu-silentdev' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising the security of applications that depend on it. Users may inadvertently install these malicious versions, leading to unauthorized access or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall enormous_emu-silentdev
If 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, users can avoid using the 'enormous_emu-silentdev' package until a patch is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'enormous_emu-silentdev' package presents a significant security risk due to its malicious behavior. Users are advised to update their packages regularly and utilize tools like Vulert to monitor for vulnerabilities. By staying informed and proactive, developers can protect their applications from potential threats.
See every vulnerability recorded for enormous_emu-silentdev →
FAQ
The package contains malicious code that modifies package.json files and republishes variants to pollute the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed 'enormous_emu-silentdev', you should remove it immediately and update to a patched version if available.
Yes, using npm packages can pose risks if they contain malicious code or vulnerabilities. Always verify the source and integrity of packages before installation.
Vulert uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities, helping developers maintain secure applications.