Malicious Code Injection in various_worm_z3n Package: A Threat to npm Ecosystem

various_worm_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97235: Malicious code in various_worm_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The various_worm_z3n package is part of a malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names, thus inflating developer reputation scores for token rewards. Its functionality is primarily centered around creating and publishing these variants, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious design of the various_worm_z3n package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages. The continuous republishing of these variants can lead to a cluttered and potentially harmful environment for developers relying on npm for legitimate packages.

How To Fix

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

npm uninstall various_worm_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 various_worm_z3n package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages and remove any that appear suspicious or are not actively maintained.

Conclusion

The various_worm_z3n package poses a significant threat to the npm ecosystem due to its malicious intent to manipulate the registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their projects are secure from such vulnerabilities.

See every vulnerability recorded for various_worm_z3n →

Share this vulnerability

FAQ

The various_worm_z3n package is a malicious npm package designed to manipulate the npm registry by generating and publishing derivative packages with randomized names.

This vulnerability can lead to the pollution of the npm registry, potentially causing conflicts and security risks in your project if you inadvertently install malicious packages.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you have installed the various_worm_z3n package, you should uninstall it immediately using npm uninstall various_worm_z3n and review your other dependencies for any similar threats.

Regularly audit your npm packages, keep your dependencies updated, and utilize tools like Vulert to monitor for open-source vulnerabilities in real-time.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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