Critical Malicious Code Vulnerability in hiagenttest Package

hiagenttest Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1950: Malicious code in hiagenttest (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 hiagenttest package is an npm library designed for testing purposes. It is commonly used in development environments to facilitate various testing scenarios. However, this package has been identified as containing malicious code, posing significant risks to any system where it is installed. The vulnerability allows attackers to gain unauthorized access to sensitive information and control over the affected systems.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the hiagenttest package. This code can compromise any computer that has the package installed, leading to potential data breaches and unauthorized access to secrets and keys stored on the system. The malicious nature of the code is classified under CWE-506, which indicates that the product contains embedded malicious code. Users should 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 hiagenttest

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. The only safe course of action is to uninstall the hiagenttest package and ensure that all sensitive information is secured.

Conclusion

The hiagenttest package contains malicious code that poses a serious threat to any system where it is installed. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for hiagenttest →

Share this vulnerability

FAQ

You should immediately uninstall the hiagenttest package and rotate any sensitive information stored on your system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Visit Vulert Scanner to check your application without needing to sign up.

Keeping hiagenttest installed can lead to unauthorized access to your system, data breaches, and potential control by malicious actors.

No, there is currently no patched version available for the hiagenttest package. The only solution is to uninstall it.

Regularly monitor your dependencies using tools like Vulert, and ensure that you only install packages from trusted sources.

How To Fix

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

npm uninstall hiagenttest

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