Malicious Code Injection in logical_pony_z3n: A Threat to npm Packages

logical_pony_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-87987: Malicious code in logical_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 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 package 'logical_pony_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often include scripts that automatically generate and publish derivative packages, compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'logical_pony_z3n' stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of developers but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.

How To Fix

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

npm uninstall logical_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 measure, you can avoid using the 'logical_pony_z3n' package and replace it with a trusted alternative. Additionally, regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.

Conclusion

The 'logical_pony_z3n' package poses a significant threat due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain the integrity of their software.

See every vulnerability recorded for logical_pony_z3n →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.

You should uninstall the package immediately using 'npm uninstall logical_pony_z3n' and check for any other affected packages.

Yes, using this package can lead to reputation damage for developers, dependency confusion, and potential exploitation of applications.

Regularly audit your dependencies, use trusted packages, and stay informed about vulnerabilities in the npm ecosystem.

How To Fix

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

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