Malicious Code Injection in leading_prawn_z3n Package

leading_prawn_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95201: Malicious code in leading_prawn_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 leading_prawn_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. Its primary functionality revolves around creating and managing these packages, but it has been compromised to include malicious scripts.

Vulnerability Detail

The vulnerability in the leading_prawn_z3n package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can cause significant issues for developers relying on the npm registry for secure package management.

How To Fix

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

npm uninstall leading_prawn_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 prevent the installation of the leading_prawn_z3n package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid the installation of this malicious package until a fix is available.

Conclusion

The leading_prawn_z3n package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to remove this package from their projects and monitor for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your project effectively.

See every vulnerability recorded for leading_prawn_z3n →

Share this vulnerability

FAQ

The leading_prawn_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and other packages you depend on.

You should remove the leading_prawn_z3n package from your project immediately and check for any updates or patches that may be released.

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

You can add 'package-lock=false' to your .npmrc file to prevent the installation of the leading_prawn_z3n package until a fix is available.

How To Fix

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

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