Malicious Code Vulnerability in evolutionary_hookworm-tool: Exploitation of npm Registry

evolutionary_hookworm-tool Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102296: Malicious code in evolutionary_hookworm-tool (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 evolutionary_hookworm-tool is an npm package that is part of a broader campaign aimed at exploiting the npm registry for token rewards. It is designed to facilitate the automatic generation and publication of derivative packages, which can mislead developers and inflate reputation scores within the npm ecosystem. This package's functionality is compromised due to its malicious intent, which poses significant risks to developers relying on it.

Vulnerability Detail

The vulnerability stems from the package being part of a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only affects the integrity of the npm ecosystem but can also lead to developers inadvertently using compromised packages, resulting in potential security breaches.

How To Fix

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

npm uninstall evolutionary_hookworm-tool

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 evolutionary_hookworm-tool package altogether. If it is already in use, consider replacing it with a reputable alternative that does not have known vulnerabilities. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The evolutionary_hookworm-tool package presents a significant security risk due to its malicious design aimed at exploiting the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining a secure development environment.

See every vulnerability recorded for evolutionary_hookworm-tool →

Share this vulnerability

FAQ

It is an npm package involved in a malicious campaign that exploits the npm registry for token rewards.

Using this package can lead to security breaches, as it modifies your package.json and can introduce malicious code.

You should remove the evolutionary_hookworm-tool package from your project immediately and monitor for any unauthorized changes.

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

Yes, 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 evolutionary_hookworm-tool

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