Malicious Code Injection in musical_hookworm_z3n Package

musical_hookworm_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106050: Malicious code in musical_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The musical_hookworm_z3n package is part of the npm ecosystem, typically used for managing JavaScript dependencies in web applications. This package, like many others, is susceptible to malicious code injections that can compromise the integrity of the software. The vulnerability stems from its association with the tea.xyz token reward campaign, which has been known to flood npm with harmful packages.

Vulnerability Detail

This vulnerability involves the injection of malicious code into the musical_hookworm_z3n package. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to potential security risks such as unauthorized access and pollution of the npm registry. The origin of this issue 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 musical_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 musical_hookworm_z3n package from your project until a secure version is released. You can do this by executing the following command: npm uninstall musical_hookworm_z3n. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The musical_hookworm_z3n package has been identified as containing malicious code that can compromise your application's security. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring.

See every vulnerability recorded for musical_hookworm_z3n →

Share this vulnerability

FAQ

musical_hookworm_z3n is an npm package used for managing JavaScript dependencies, but it has been identified as containing malicious code.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's security and integrity.

You should immediately update the package to a patched version or remove it from your project until a secure version is available.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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