Malicious Code Injection in Developing Python Z3N Package - npm Vulnerability

developing_python_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101400: Malicious code in developing_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'developing_python_z3n' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of Python-related functionalities in JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system, leading to significant security concerns.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the 'developing_python_z3n' package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. This behavior not only inflates developer reputation scores fraudulently but also pollutes the npm registry with potentially harmful packages, posing a risk to developers who may unknowingly install these variants.

How To Fix

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

npm uninstall developing_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 measure, you can avoid using the 'developing_python_z3n' package and look for alternative packages that provide similar functionalities without the associated risks. Additionally, you can use the following command to audit your npm packages for vulnerabilities: 'npm audit'.

Conclusion

The 'developing_python_z3n' package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is essential for developers to uninstall this package and monitor their projects for vulnerabilities to maintain security.

See every vulnerability recorded for developing_python_z3n →

Share this vulnerability

FAQ

It is an npm package intended for Python-related functionalities in JavaScript applications, but it has been compromised with malicious code.

The malicious code can modify your package.json, remove private flags, and republish variants, leading to potential security risks and pollution of the npm registry.

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

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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