Malicious Code Injection in likely_squid_z3n Package
Summary
MAL-2025-95255: Malicious code in likely_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 likely_squid_z3n package is part of the npm ecosystem, often associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which 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 affecting other developers by inflating reputation scores through deceptive practices. The malicious scripts are typically named auto.js, autopublish.js, autopublish2.js, and autopublish3.js, which automate these harmful actions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall likely_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 workaround, you can avoid using the likely_squid_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The likely_squid_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Immediate action is required to remove this package and safeguard your project from potential exploitation. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for likely_squid_z3n →
FAQ
likely_squid_z3n is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of packages.
The vulnerability can lead to unauthorized changes in your package.json file, potentially compromising your project's integrity and reputation in the npm registry.
You should uninstall the likely_squid_z3n package immediately using the command npm uninstall likely_squid_z3n to prevent any malicious actions.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
Regularly audit your dependencies using tools like npm audit, and stay informed about vulnerabilities in the packages you use. Consider using Vulert for real-time monitoring.
