Malicious Code Injection in permanent_mockingbird_z3n: A Threat to npm Packages
Summary
MAL-2025-89460: Malicious code in permanent_mockingbird_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 permanent_mockingbird_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 essential files, thereby compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in permanent_mockingbird_z3n originates from its inclusion in a malicious campaign aimed at manipulating the npm ecosystem. It contains scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall permanent_mockingbird_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, you can avoid using the permanent_mockingbird_z3n package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages to identify and remove any suspicious or untrusted packages.
Conclusion
The permanent_mockingbird_z3n package poses a significant threat to the integrity of npm packages due to its malicious behavior. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for permanent_mockingbird_z3n →
FAQ
Permanent_mockingbird_z3n 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 lead to the pollution of the npm registry, potentially affecting your project's dependencies and overall security.
You should uninstall the permanent_mockingbird_z3n package immediately and audit your other dependencies for any related vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground.
There is no patch for the permanent_mockingbird_z3n package as it is recommended to remove it entirely from your project.
