Malicious Code Injection in distant_barnacle_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-94062: Malicious code in distant_barnacle_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 distant_barnacle_z3n package is part of a campaign that exploits the npm ecosystem, primarily targeting developers involved with the tea.xyz token reward initiative. This package, like others in the campaign, is designed to automatically generate and publish derivative packages with randomized names. Its functionality is compromised by malicious scripts that manipulate package metadata, leading to potential reputational damage for developers and pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from malicious code embedded in the distant_barnacle_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts are designed to continuously republish these variants, which can inflate developer reputation scores fraudulently and clutter the npm registry with unwanted packages. The ramifications include potential security risks for applications relying on these packages, as well as reputational harm to developers who may unknowingly use or be associated with these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall distant_barnacle_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 distant_barnacle_z3n package and monitor your dependencies for any updates or patches. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The distant_barnacle_z3n package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with unwanted variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for distant_barnacle_z3n →
FAQ
The distant_barnacle_z3n package is part of a malicious campaign targeting the npm ecosystem, designed to inflate developer reputation scores through automated publishing.
The malicious code modifies your package.json file, potentially exposing your project to security risks and cluttering the npm registry with unwanted packages.
You should uninstall the distant_barnacle_z3n package immediately using the command: npm uninstall distant_barnacle_z3n.
Yes, you can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Absolutely! You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
