Malicious Code Injection in ultimate_worm_z3n: A Threat to npm Ecosystem

ultimate_worm_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109971: Malicious code in ultimate_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 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 package 'ultimate_worm_z3n' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by generating and publishing numerous derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in 'ultimate_worm_z3n' originates from its inclusion in a malicious campaign that utilizes autopublish scripts to manipulate package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, leading to a significant risk of registry pollution and potential exploitation by malicious actors. The continuous republishing of these variants can compromise the integrity of the npm ecosystem.

How To Fix

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

npm uninstall ultimate_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 measure, you can avoid using the 'ultimate_worm_z3n' package and monitor your project for any unintended dependencies that may have been introduced. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The 'ultimate_worm_z3n' package poses a significant threat to the npm ecosystem due to its malicious intent to manipulate package data and republish variants. It is crucial for developers to be vigilant, remove such packages, and utilize monitoring tools like Vulert to safeguard their projects.

See every vulnerability recorded for ultimate_worm_z3n →

Share this vulnerability

FAQ

The ultimate_worm_z3n package is a malicious npm package that is part of a campaign to inflate developer reputation scores by generating and publishing numerous derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and exposing it to further risks.

You can use the Vulert platform to monitor your package-lock.json for vulnerabilities without requiring any code access or installation.

You should uninstall the package immediately using 'npm uninstall ultimate_worm_z3n' and review your project for any other potentially malicious dependencies.

Yes, regularly updating your dependencies, using tools like Vulert for monitoring, and reviewing your package-lock.json can help prevent similar vulnerabilities.

How To Fix

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

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