Malicious Code Injection in constitutional_hookworm_z3n Package

constitutional_hookworm_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93751: Malicious code in constitutional_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 constitutional_hookworm_z3n package is part of the tea.xyz token reward campaign that has recently infiltrated the npm ecosystem. This package is designed to facilitate token rewards through the automatic generation and publication of derivative packages. However, it has been identified as containing malicious scripts that compromise its integrity and the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the constitutional_hookworm_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to security risks for users who unknowingly install these compromised packages.

How To Fix

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

npm uninstall constitutional_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 constitutional_hookworm_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The constitutional_hookworm_z3n package poses a significant risk due to its malicious code that alters package metadata and republishing behavior. It is essential to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for constitutional_hookworm_z3n →

Share this vulnerability

FAQ

It is a package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of npm packages.

The malicious code can modify your package.json, remove private flags, and publish unauthorized packages, potentially leading to security vulnerabilities.

You should uninstall the package immediately using 'npm uninstall constitutional_hookworm_z3n' and check your project for any dependencies that may be affected.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Absolutely! You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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