Critical Malicious Code Vulnerability in hiagentevilmcp Package

hiagentevilmcp Updated 03 Mar 2026

Summary

03/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1178: Malicious code in hiagentevilmcp (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 hiagentevilmcp package is an npm module that is intended for use in JavaScript applications. It is designed to provide certain functionalities that developers can leverage in their projects. However, this package has been identified as containing malicious code, which poses a significant risk to any system where it is installed. The presence of such code can lead to unauthorized access and control over the affected systems.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the hiagentevilmcp package. This code is designed to compromise the security of any computer that has the package installed, allowing an external entity to gain full control over the system. The ramifications of this vulnerability are severe, as it can lead to the exposure of sensitive information, including secrets and keys stored on the compromised machine. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall hiagentevilmcp

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

There are no effective workarounds for this vulnerability other than removing the package entirely. Ensure that you monitor your systems for any signs of unauthorized access after removal.

Conclusion

The hiagentevilmcp package contains malicious code that poses a significant risk to any system where it is installed. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring and vulnerability checks are essential to maintain the security of your applications.

See every vulnerability recorded for hiagentevilmcp →

Share this vulnerability

FAQ

Immediately uninstall the package using npm uninstall hiagentevilmcp and rotate any sensitive information stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Keeping the hiagentevilmcp package installed can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

After removing the package, you should rotate all secrets and keys stored on the compromised machine and monitor for any unusual activity.

While many npm packages are safe, it is crucial to verify the integrity of packages before installation. Regularly check for vulnerabilities using tools like Vulert.

How To Fix

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

npm uninstall hiagentevilmcp

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