Malicious Code Injection in missing_hookworm_z3n Package - npm Vulnerability

missing_hookworm_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105895: Malicious code in missing_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The missing_hookworm_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be associated with a token reward campaign that has led to the proliferation of malicious packages. These packages often contain scripts designed to manipulate the npm registry, potentially compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in the missing_hookworm_z3n package arises from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been identified as a source of numerous malicious packages.

How To Fix

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

npm uninstall missing_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 avoid using the missing_hookworm_z3n package and any other packages that may be associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The missing_hookworm_z3n package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and monitor your dependencies to maintain the integrity of your software. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities.

See every vulnerability recorded for missing_hookworm_z3n →

Share this vulnerability

FAQ

The missing_hookworm_z3n package is an npm package that has been identified as malicious, associated with a token reward campaign that floods the npm registry with harmful packages.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to pollution of the npm registry and compromise the integrity of your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By simply using your package-lock.json file, you can check for vulnerabilities without needing to install any software.

If you have installed the missing_hookworm_z3n package, you should uninstall it immediately using 'npm uninstall missing_hookworm_z3n' and check your package-lock.json for any references.

To prevent similar vulnerabilities, regularly audit your dependencies using tools like npm audit, and consider using Vulert to monitor your projects for real-time alerts on open-source vulnerabilities.

How To Fix

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

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