Malicious Code Injection in occupational_puffin_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95731: Malicious code in occupational_puffin_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 'occupational_puffin_z3n' is part of a series of npm packages that have been linked to 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. This behavior poses a significant risk to the integrity of the npm registry and the applications that depend on these packages.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the 'occupational_puffin_z3n' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, resulting in the continuous republishing of variants. This behavior can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall occupational_puffin_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 'occupational_puffin_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'occupational_puffin_z3n' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remove this package and monitor their projects for any potential vulnerabilities.
See every vulnerability recorded for occupational_puffin_z3n →
FAQ
The main risk is the potential for malicious code to alter your project's dependencies and compromise the integrity of your application.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall occupational_puffin_z3n' and review your project's dependencies for any other vulnerabilities.
Yes, you should look for reputable packages that offer similar functionality but do not have a history of malicious behavior.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and only install packages from trusted sources.
