Malicious Code Injection in soft_earwig_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96657: Malicious code in soft_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 'soft_earwig_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in 'soft_earwig_z3n' stems from its malicious payload that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly incorporate these malicious packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall soft_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 avoid using the 'soft_earwig_z3n' package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'soft_earwig_z3n' package poses a significant risk to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and take proactive measures to secure their projects by removing such packages and utilizing tools like Vulert for ongoing monitoring.
See every vulnerability recorded for soft_earwig_z3n →
FAQ
The primary threat is the malicious code that modifies package.json files, removes private flags, and generates random package names, leading to pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your application is affected.
You should uninstall the 'soft_earwig_z3n' package immediately using 'npm uninstall soft_earwig_z3n' and look for alternative packages.
Regularly audit your dependencies using tools like Vulert and keep your packages updated to the latest versions to minimize risks.
You can find detailed information about this vulnerability in the official npm registry or by visiting the GitHub repository for malicious packages.
