Malicious Code Injection in skilled_bug_z3n Package - npm Vulnerability
Summary
MAL-2025-98931: Malicious code in skilled_bug_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The skilled_bug_z3n package is part of the npm ecosystem and has been identified as a component of 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. Its functionality is compromised due to the presence of malicious code that alters package metadata.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the skilled_bug_z3n package. This code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The malicious payload continuously republishes these variants to pollute the npm registry, posing a risk to developers who may unknowingly use these compromised packages. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded the npm registry with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall skilled_bug_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 skilled_bug_z3n package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The skilled_bug_z3n package has been identified as a malicious component within the npm ecosystem, posing significant risks to developers. It is crucial to remove this package and monitor your dependencies to ensure the security of your projects. Utilizing tools like Vulert can aid in maintaining awareness of potential vulnerabilities.
See every vulnerability recorded for skilled_bug_z3n →
FAQ
The skilled_bug_z3n package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The malicious code modifies your package.json file, potentially leading to the publication of compromised packages and exposing your project to security risks.
You should immediately remove the skilled_bug_z3n package from your project and monitor your dependencies for any unusual activity.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time, alerting you to any issues.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
