Malicious Code Injection in endless_python_z3n Package - npm Vulnerability

endless_python_z3n Updated 25 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-133098: Malicious code in endless_python_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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The endless_python_z3n package is part of the npm ecosystem, often used in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages on npm. This package is designed to generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the endless_python_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This can result in security risks for developers who unknowingly integrate these malicious packages into their projects, potentially compromising their applications.

How To Fix

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

npm uninstall endless_python_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 endless_python_z3n package from your project by executing the following command: npm uninstall endless_python_z3n. Additionally, you can use Vulert to monitor your project for vulnerabilities by checking your package-lock.json file. Visit https://vulert.com/scanner to assess if your application is affected by this vulnerability without needing to sign up.

Conclusion

The endless_python_z3n package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your projects.

See every vulnerability recorded for endless_python_z3n →

Share this vulnerability

FAQ

endless_python_z3n is an npm package associated with a token reward campaign that has been identified as malicious due to its behavior of generating and publishing derivative packages.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and functionality.

If you have installed the endless_python_z3n package, it is recommended to uninstall it immediately and check for any other affected packages.

You can use Vulert to monitor your project for open-source vulnerabilities by analyzing your package-lock.json file. Visit Vulert Scanner for more information.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to your packages.

How To Fix

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

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