Malicious Code Vulnerability in test1ro Package

test1ro Updated 21 Sep 2026

Summary

21/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16315: Malicious code in test1ro (npm). Affects test1ro versions 99.99.99 – 999.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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The test1ro package is an npm module that is designed for use in JavaScript applications. It is typically utilized for various functionalities within the Node.js ecosystem. However, this package has been found to contain malicious code that can compromise the security of systems using it. The vulnerability arises from preinstall and postinstall hooks that execute code without user consent, potentially leading to data leakage and unauthorized access.

Vulnerability Detail

The vulnerability in the test1ro package stems from its preinstall and postinstall hooks that execute a script (node index.js) during the npm install process. This script retrieves the host's identifier using os.hostname() and sends it to a hardcoded external server (http://eo8f3m3ho26a0nm.m.pipedream.net/<package>?h=<hostname>). This behavior allows the attacker to collect sensitive information about the user's environment without their knowledge. The package also uses a high version number (999.99.99) to exploit dependency confusion, which could lead to the installation of malicious code instead of the intended internal package.

How To Fix

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

npm uninstall test1ro

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 test1ro package altogether. If it is already installed, you can uninstall it using the command: npm uninstall test1ro. Additionally, consider using a tool like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.

Conclusion

The test1ro package contains a serious vulnerability that can compromise user data and system security. It is crucial to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help keep your applications secure by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for test1ro →

Share this vulnerability

FAQ

The test1ro package is an npm module used in JavaScript applications, but it has been found to contain malicious code.

The vulnerability executes malicious code during the installation process, sending sensitive information to an external server.

You should uninstall the test1ro package immediately using the command: npm uninstall test1ro.

Currently, there is no patched version available for the test1ro package. Monitor the repository for updates.

Vulert can monitor your package-lock.json file for vulnerabilities in real-time, alerting you to any issues without requiring code access.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall test1ro

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