Malicious Code Execution in test1df23 Package

test1df23 Updated 21 Sep 2026

Summary

21/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16312: Malicious code in test1df23 (npm). Affects test1df23 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 test1df23 package is an npm module that is intended for use in JavaScript applications. It is designed to facilitate certain functionalities within the npm ecosystem. However, this package has been identified as containing malicious code that executes upon installation, posing significant security risks to users and their systems.

Vulnerability Detail

The vulnerability stems from the presence of preinstall and postinstall hooks in the package.json file of test1df23. These hooks trigger the execution of index.js during the npm install process. The index.js file contains code that sends an HTTP GET request to a hardcoded IP address (128.199.122.145) over plain HTTP, embedding the package name in the query string. This action leaks the installer's outbound IP address and confirms the successful execution of the code to the operator of that IP. This behavior is indicative of a dependency-confusion or typosquatting attack, which can lead to unauthorized access and data leakage.

How To Fix

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

npm uninstall test1df23

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 test1df23 package altogether. If it is already installed, you can uninstall it using the command: npm uninstall test1df23. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The test1df23 package contains malicious code that poses significant security risks to users. It is essential to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for test1df23 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that executes during the installation of the package, which can leak sensitive information.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring access to the code.

If you have installed test1df23, it is recommended to uninstall it immediately using the command: npm uninstall test1df23.

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

Using malicious packages can lead to data breaches, unauthorized access to systems, and potential compromise of sensitive information.

How To Fix

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

npm uninstall test1df23

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