Malicious Code Injection in notable_pelican_z3n Package
Summary
MAL-2025-106393: Malicious code in notable_pelican_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 notable_pelican_z3n package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages. This vulnerability exposes users to potential security risks as it modifies essential files and repackages them under random names.
Vulnerability Detail
The vulnerability originates from a malicious campaign linked to the tea.xyz token reward initiative. The notable_pelican_z3n package contains scripts that automatically generate and publish derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies the package.json file by removing private flags and altering version numbers. The ramifications include compromised package integrity, potential exposure of sensitive information, and a degraded developer reputation due to the proliferation of low-quality packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall notable_pelican_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 prevent the installation of the notable_pelican_z3n package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help mitigate the risk until a permanent fix is applied.
Conclusion
The notable_pelican_z3n package poses a significant security risk due to its malicious code that modifies essential project files and proliferates low-quality packages. It is essential to remove this package and monitor for updates to ensure the integrity of your project.
See every vulnerability recorded for notable_pelican_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the modification of your package.json file, exposure of sensitive information, and the proliferation of low-quality packages in your project.
You should remove the notable_pelican_z3n package from your project and monitor for any updates or patches.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without 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.
