Malicious Code Vulnerability in test1hh235 Package

test1hh235 Updated 21 Sep 2026

Summary

21/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16314: Malicious code in test1hh235 (npm). Affects test1hh235 versions 99.99.99. 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 test1hh235 package is an npm package that is designed for use in JavaScript applications. It is intended to provide specific functionalities to developers. However, this package has been identified as containing malicious code that can compromise the security of applications using it. The vulnerability arises from lifecycle hooks that execute code during installation, which can lead to unauthorized data exfiltration.

Vulnerability Detail

The vulnerability in the test1hh235 package originates from its preinstall and postinstall lifecycle hooks that execute a script (index.js) upon installation. This script makes an HTTP GET request to a hardcoded IP address (128.199.122.145), embedding the package name in the query string. This behavior indicates a reconnaissance probe for dependency confusion attacks, where the package's implausibly high version number (99.99.99) is designed to win resolution against internal packages. The automatic execution of this script during installation allows attackers to confirm the target environment, potentially leading to further exploitation.

How To Fix

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

npm uninstall test1hh235

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 workaround, you can avoid using the test1hh235 package altogether. If it is already installed, you can uninstall it using the command: npm uninstall test1hh235. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without requiring any signup.

Conclusion

The test1hh235 package has been identified as containing malicious code that poses a significant security risk. Users are advised to uninstall the package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for test1hh235 →

Share this vulnerability

FAQ

The test1hh235 package is an npm package used in JavaScript applications, but it has been identified as containing malicious code.

The vulnerability executes a script during installation that sends data to an attacker-controlled server, potentially exposing sensitive information.

You should uninstall the test1hh235 package immediately and check for any other dependencies that may be affected.

Currently, there is no patched version available. It is advised to remove the package until a secure version is released.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

How To Fix

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

npm uninstall test1hh235

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