Malicious Code Injection in precise_mole_z3n Package

precise_mole_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95970: Malicious code in precise_mole_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 precise_mole_z3n package is part of the npm ecosystem, often associated with token reward campaigns. It is designed to facilitate the publication of JavaScript packages. However, this package has been identified as malicious, containing scripts that manipulate its own metadata and publish numerous derivative packages to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the precise_mole_z3n package stems from its malicious code, which 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 these variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood the npm registry with such malicious packages.

How To Fix

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

npm uninstall precise_mole_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 prevent the installation of the precise_mole_z3n package by adding it to your package.json file under the 'resolutions' field, specifying a version that does not exist or is known to be safe. Example: "resolutions": { "precise_mole_z3n": "0.0.0" }.

Conclusion

The precise_mole_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is essential to remove this package from your projects and monitor for similar vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for precise_mole_z3n →

Share this vulnerability

FAQ

The precise_mole_z3n package is an npm package that has been identified as malicious, designed to manipulate its own metadata and publish numerous derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and affecting its reputation.

If you have installed the precise_mole_z3n package, it is recommended to uninstall it immediately and check for any dependencies that may be affected.

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

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with the latest security advisories.

How To Fix

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

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