Malicious Code Injection in atomic_earwig_z3n: A Threat to npm Packages
Summary
MAL-2025-99649: Malicious code in atomic_earwig_z3n (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 'atomic_earwig_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages.
Vulnerability Detail
The vulnerability in 'atomic_earwig_z3n' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect developers by misleading them about the authenticity and security of their dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall atomic_earwig_z3nIf 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 prevent the installation of this malicious package by using the following command to uninstall it: 'npm uninstall atomic_earwig_z3n'. Additionally, ensure that your package-lock.json is monitored for any unauthorized changes.
Conclusion
The 'atomic_earwig_z3n' package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. Immediate action is required to mitigate these risks by updating or removing the package. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.
See every vulnerability recorded for atomic_earwig_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry and compromise the integrity of other packages, affecting developers and their applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If no patched version is available, it is advisable to remove the package from your project to mitigate the risk.
The payload modifies the package.json file, removing private flags and changing version numbers, which allows for the automated generation and republishing of derivative packages.
Regularly audit your dependencies, use tools like Vulert for monitoring, and be cautious when adding new packages from unknown sources.
