Malicious Code Injection in metropolitan_hookworm_z3n: A Threat to npm Packages

metropolitan_hookworm_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105810: Malicious code in metropolitan_hookworm_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 metropolitan_hookworm_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality has been compromised, making it a potential threat to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in metropolitan_hookworm_z3n arises from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to create and republish derivative packages, polluting the npm registry and potentially leading to security risks for developers who unknowingly install these compromised packages. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which exploits npm's package management system.

How To Fix

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

npm uninstall metropolitan_hookworm_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 remove the metropolitan_hookworm_z3n package from your project by executing the following command: npm uninstall metropolitan_hookworm_z3n. This will prevent any malicious code from executing in your environment until a secure version is available.

Conclusion

The metropolitan_hookworm_z3n package poses a significant risk due to its malicious code that alters package management processes. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for metropolitan_hookworm_z3n →

Share this vulnerability

FAQ

metropolitan_hookworm_z3n is an npm package that has been identified as containing malicious code aimed at manipulating package management processes.

The malicious code modifies your package.json file, potentially leading to the installation of compromised packages and security vulnerabilities in your project.

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

Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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