Malicious Code Injection in obedient_hookworm_0xrequest Package

obedient_hookworm_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106474: Malicious code in obedient_hookworm_0xrequest (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 obedient_hookworm_0xrequest package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package is involved in generating and publishing derivative packages with randomized names, which can lead to reputation inflation and registry pollution.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods npm with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to potential security risks and abuse of the npm registry. This can result in developers unknowingly using compromised packages, which may contain harmful scripts.

How To Fix

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

npm uninstall obedient_hookworm_0xrequest

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 obedient_hookworm_0xrequest package from your project by executing: npm uninstall obedient_hookworm_0xrequest. This will prevent any malicious code from executing until a fix is applied.

Conclusion

The obedient_hookworm_0xrequest package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications from potential threats.

See every vulnerability recorded for obedient_hookworm_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

You should immediately update or uninstall the package to prevent any security risks associated with its use.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

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

How To Fix

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

npm uninstall obedient_hookworm_0xrequest

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