Critical Malicious Code Vulnerability in testrrrd Package

testrrrd Updated 09 Oct 2026

Summary

08/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17706: Malicious code in testrrrd (npm). Affects testrrrd versions 0.0.1 – 99.0.1. 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 testrrrd package is an npm module designed for testing and development purposes. It provides various functionalities that developers can utilize in their applications. However, this package has been found to contain malicious code that compromises user data and system integrity, making it a significant security risk.

Vulnerability Detail

The vulnerability originates from the package's post-installation script, which executes a malicious beacon script (beacon.cjs) upon installation. This script sends sensitive information, including the installer's hostname, install path, current working directory, Node version, and package identifier, to a hardcoded IP address over unencrypted HTTP. This behavior poses a serious risk as it can lead to unauthorized data exposure and potential exploitation of the user's system. The malicious code is designed to trigger even when lifecycle scripts are suppressed, ensuring that the beacon is sent regardless of user intent.

How To Fix

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

npm uninstall testrrrd

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 measure, you can avoid using the testrrrd package altogether. If you must use it, consider running your application in a controlled environment where sensitive data is not exposed, or use tools like Vulert to monitor for vulnerabilities in your package-lock.json file.

Conclusion

The testrrrd package has been identified as containing malicious code that compromises user data and system integrity. It is crucial for developers to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.

See every vulnerability recorded for testrrrd →

Share this vulnerability

FAQ

The testrrrd package is an npm module used for testing and development purposes in JavaScript applications.

The malicious code runs a script that sends sensitive information to a hardcoded IP address whenever the package is installed or imported.

The risks include unauthorized data exposure, potential exploitation of the user's system, and loss of privacy.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

You should remove the testrrrd package from your project immediately and monitor for any updates or patches that may be released.

How To Fix

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

npm uninstall testrrrd

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