Malicious Code Injection in proper_python_z3n: A Threat to npm Ecosystem

proper_python_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89529: Malicious code in proper_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'proper_python_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm registry and poses a significant risk to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability in 'proper_python_z3n' originates from its association with the tea.xyz token reward campaign. This package contains scripts designed to automatically modify its own package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers.

How To Fix

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

npm uninstall proper_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 avoid using the 'proper_python_z3n' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: 'npm uninstall proper_python_z3n'.

Conclusion

The 'proper_python_z3n' package poses a significant security risk due to its malicious code that modifies package metadata and repackages itself. It is essential for developers to remove this package from their projects and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for proper_python_z3n →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json and repackages itself under random names, leading to potential security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

You should uninstall the package immediately using 'npm uninstall proper_python_z3n' and look for safer alternatives.

Yes, the vulnerability can lead to the installation of compromised packages, which may introduce further security risks to your application.

While a patch has not been released yet, it is advisable to monitor the npm registry for updates and security advisories regarding the package.

How To Fix

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

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.