Critical Malicious Code Vulnerability in systemtest-information Package

systemtest-information Updated 11 Feb 2026

Summary

11/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-858: Malicious code in systemtest-information (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 systemtest-information package is an npm library designed for testing and system information retrieval. It is commonly used in development environments to facilitate automated testing and system diagnostics. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the systemtest-information package. This code can grant unauthorized access to the system, allowing attackers to control the compromised machine fully. The ramifications are severe, as all secrets and keys stored on the affected computer are at risk. Users are advised to treat any system with this package installed as fully compromised, necessitating immediate action to secure sensitive information.

How To Fix

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

npm uninstall systemtest-information

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

There are no effective workarounds for this vulnerability other than removing the package entirely. If you need similar functionality, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the systemtest-information package poses a significant threat to users. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for systemtest-information →

Share this vulnerability

FAQ

You should uninstall the package immediately using the command 'npm uninstall systemtest-information' and rotate any sensitive information stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

While many npm packages are safe, it is essential to verify the integrity of packages before installation and to keep an eye on security advisories.

How To Fix

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

npm uninstall systemtest-information

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