Malicious Code Injection in basic_tiglon_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-93359: Malicious code in basic_tiglon_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 'basic_tiglon_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'basic_tiglon_z3n' originates from its inclusion in a malicious campaign that uses autopublish scripts to manipulate package.json files. This manipulation involves removing private flags, altering version numbers, and generating random package names, which can lead to significant pollution of the npm registry. The ramifications include compromised package integrity, potential security risks for developers using these packages, and a degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall basic_tiglon_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, avoid using the 'basic_tiglon_z3n' package and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.
Conclusion
The 'basic_tiglon_z3n' package poses a significant threat to the npm ecosystem due to its malicious code that alters package files and republish variants. It is crucial for developers to be vigilant and remove any affected packages from their projects while utilizing tools like Vulert for ongoing monitoring.
See every vulnerability recorded for basic_tiglon_z3n →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can compromise the integrity of your project by introducing malicious code and polluting the npm registry with untrustworthy packages.
You should uninstall the package immediately using 'npm uninstall basic_tiglon_z3n' and check for any other affected packages in your project.
You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
