Malicious Code Injection in local_squid_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95301: Malicious code in local_squid_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 local_squid_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 linked to the distribution of malicious packages. These packages often contain scripts designed to manipulate the npm registry by generating and publishing derivative packages with altered metadata, thereby inflating developer reputation scores.
Vulnerability Detail
The vulnerability in local_squid_z3n stems from its malicious code that modifies the package.json file to remove private flags, changes 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 the ecosystem. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall local_squid_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 measure, you can prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. You can also utilize the following command to audit your project for vulnerabilities: npm audit.
Conclusion
The local_squid_z3n package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata. It is crucial for developers to be aware of this vulnerability and take immediate action to remove the affected package and monitor their projects for potential risks.
See every vulnerability recorded for local_squid_z3n →
FAQ
local_squid_z3n is an npm package that has been identified as malicious, associated with the tea.xyz token reward campaign.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
You should remove the package from your project immediately and check for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
