Malicious Code Injection in normal_pony_z3n Package - npm Vulnerability

normal_pony_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95664: Malicious code in normal_pony_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The normal_pony_z3n package is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with random names, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the normal_pony_z3n package. This code modifies the package.json file by removing private flags, changing version numbers, and generating random package names, which leads to the continuous republishing of these variants. The ramifications include potential pollution of the npm registry, unauthorized access to sensitive information, and damage to developer reputations. The malicious payload is executed through autopublish scripts that automate the creation and publication of these compromised packages.

How To Fix

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

npm uninstall normal_pony_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, avoid using the normal_pony_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure no malicious packages are included.

Conclusion

The normal_pony_z3n package poses a significant security risk due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining a secure development environment.

See every vulnerability recorded for normal_pony_z3n →

Share this vulnerability

FAQ

normal_pony_z3n is an npm package that has been identified as malicious, designed to manipulate the npm registry and inflate developer reputation scores.

The malicious code modifies your package.json file, potentially exposing sensitive information and leading to the pollution of the npm registry.

You should uninstall the normal_pony_z3n package immediately using the command npm uninstall normal_pony_z3n.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, consider using other reputable packages that offer similar functionality without the risks associated with normal_pony_z3n.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall normal_pony_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