Malicious Code Injection in crowded_worm_z3n Package - npm Vulnerability

crowded_worm_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101101: Malicious code in crowded_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 crowded_worm_z3n package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The primary functionality of this package is to serve as a tool for developers, but its malicious nature compromises the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the crowded_worm_z3n package arises from its inclusion in a malicious campaign that floods the npm registry with harmful packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the pollution of the npm registry and can potentially harm developers by affecting their reputation and the reliability of their dependencies.

How To Fix

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

npm uninstall crowded_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 workaround, consider using a package-lock.json file to monitor your dependencies. This file helps in identifying and locking the versions of packages used in your project, thereby preventing the installation of malicious packages. You can also utilize tools like Vulert to monitor for vulnerabilities in real-time without requiring code access or installation.

Conclusion

The crowded_worm_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior of flooding the registry with harmful packages. It is crucial for developers to be vigilant, remove affected packages, and utilize monitoring tools to safeguard their projects from such vulnerabilities.

See every vulnerability recorded for crowded_worm_z3n →

Share this vulnerability

FAQ

crowded_worm_z3n is a malicious npm package that is part of a campaign to inflate developer reputation scores by flooding the npm registry with harmful packages.

This vulnerability can lead to the pollution of the npm registry, potentially harming your project's integrity and affecting your reputation as a developer.

You should uninstall the crowded_worm_z3n package immediately and check for any other affected packages in your project.

Yes, using a package-lock.json file and monitoring tools like Vulert can help you track and manage vulnerabilities in your dependencies.

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

How To Fix

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

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