Malicious Code Injection in odd_pelican_z3n Package

odd_pelican_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98845: Malicious code in odd_pelican_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The odd_pelican_z3n package is part of the npm ecosystem and is associated with 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. However, it has been identified as containing malicious code that modifies its own package.json file and repackages itself with random names, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the proliferation of untrustworthy packages, compromising the integrity of the npm ecosystem and potentially affecting 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 odd_pelican_z3n

If 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 remove the odd_pelican_z3n package from your project to prevent any malicious activity. Use the following command: npm uninstall odd_pelican_z3n.

Conclusion

The odd_pelican_z3n package has been identified as containing malicious code that can compromise the integrity of the npm registry. It is crucial to take immediate action by uninstalling the package and monitoring your project for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for odd_pelican_z3n →

Share this vulnerability

FAQ

odd_pelican_z3n is an npm package associated with a token reward campaign that has been identified as containing malicious code.

The vulnerability can lead to the automatic generation of untrustworthy packages, which may compromise your project's integrity and security.

You should uninstall the odd_pelican_z3n package immediately and check for any other affected packages in your project.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly update your dependencies, use tools like Vulert to monitor for vulnerabilities, and review the packages you include in your project.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall odd_pelican_z3n

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback