Malicious Code Injection in variable_llama_z3n: A Threat to npm Packages
Summary
MAL-2025-110339: Malicious code in variable_llama_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 'variable_llama_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which are intended to inflate developer reputation scores for rewards. However, it has been compromised to include malicious scripts that can alter package configurations and pollute the npm registry.
Vulnerability Detail
The vulnerability in 'variable_llama_z3n' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This can lead to the proliferation of untrustworthy packages in the npm registry, potentially harming developers and users by compromising the integrity of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall variable_llama_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 remove the 'variable_llama_z3n' package from your project by running: 'npm uninstall variable_llama_z3n'. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The 'variable_llama_z3n' package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry with untrustworthy packages. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring.
See every vulnerability recorded for variable_llama_z3n →
FAQ
The vulnerability involves malicious code that modifies package configurations and publishes untrustworthy packages to the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Using the compromised package can lead to security breaches, as it may allow unauthorized access to your application or introduce other vulnerabilities.
Regularly updating packages, using tools like Vulert for monitoring, and auditing your dependencies can help prevent vulnerabilities.
Immediately uninstall the package and check for any unauthorized changes in your project. Consider updating to a secure version if available.
