Critical Malicious Code Vulnerability in rt-qa-sampler Package

rt-qa-sampler Updated 08 Jan 2026

Summary

07/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-142: Malicious code in rt-qa-sampler (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The rt-qa-sampler package is an npm library designed for quality assurance sampling in software development. It provides tools for testing and validating software components. However, this package has been identified to contain malicious code, posing a significant security risk to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the rt-qa-sampler package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. Once installed, the package grants full control of the affected computer to an external entity, making it imperative for users to act swiftly to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall rt-qa-sampler

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, ensure that the rt-qa-sampler package is uninstalled using the following command in your terminal: npm uninstall rt-qa-sampler. Additionally, monitor your system for any unusual activity and consider using security tools to scan for remaining malicious software.

Conclusion

The rt-qa-sampler package contains a critical vulnerability due to embedded malicious code. Immediate action is required to uninstall the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their applications.

See every vulnerability recorded for rt-qa-sampler →

Share this vulnerability

FAQ

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

No, there is currently no patched version of the rt-qa-sampler package available.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete compromise of your system.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed.

How To Fix

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

npm uninstall rt-qa-sampler

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