Malicious Code Vulnerability in blank_lemming_z3n Package
Summary
MAL-2025-98629: Malicious code in blank_lemming_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 blank_lemming_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior not only compromises the integrity of the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in the blank_lemming_z3n package originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This leads to the continuous republishing of variants that pollute the npm registry, potentially affecting developers who rely on npm for legitimate packages. The ramifications include the risk of integrating malicious code into applications, which can lead to security breaches and loss 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 blank_lemming_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, avoid using the blank_lemming_z3n package and monitor your dependencies for any signs of malicious activity. You can use tools like Vulert to check your application for vulnerabilities without needing to access the code directly. Simply upload your package-lock.json file to the Vulert playground at https://vulert.com/scanner to see if your application is affected.
Conclusion
The blank_lemming_z3n package poses a significant security risk due to its malicious code designed to manipulate the npm registry. Developers are advised to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive is essential in maintaining the security of your applications.
See every vulnerability recorded for blank_lemming_z3n →
FAQ
The blank_lemming_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the integration of malicious code into your application, posing security risks and potentially compromising your system.
You should uninstall the blank_lemming_z3n package immediately and check your package-lock.json file for any references to it.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities by analyzing your package-lock.json file.
Regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.
