Malicious Code Detected in test-npm-style Package: Security Risk Identified

test-npm-style Updated 05 Feb 2026

Summary

05/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-771: Malicious code in test-npm-style (npm). Affects test-npm-style versions 1.0.11 – 1.0.9. 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 'test-npm-style' package is a Node.js library available through npm, designed to facilitate testing styles in JavaScript applications. It is utilized by developers to streamline the process of testing and ensuring the quality of their code. However, this package has been flagged for containing malicious code that communicates with a domain associated with harmful activities, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the 'test-npm-style' package arises from its version 1.0.11, which has been identified as malicious by the OpenSSF Package Analysis project. The package's malicious behavior includes communication with a domain linked to malicious activities, potentially leading to data breaches, unauthorized access, or other security incidents. This vulnerability is particularly concerning for developers who may unknowingly integrate this package into their applications, exposing them to various cyber threats.

How To Fix

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

npm uninstall test-npm-style

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, developers can remove the 'test-npm-style' package from their project until a secure version is confirmed. This can be done using the following command: npm uninstall test-npm-style. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'test-npm-style' package has been identified as malicious, posing significant security risks to applications that utilize it. Developers are strongly advised to update to the latest version to mitigate these risks and ensure the security of their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for test-npm-style →

Share this vulnerability

FAQ

The 'test-npm-style' package is a Node.js library used for testing styles in JavaScript applications, helping developers maintain code quality.

The malicious behavior was identified by the OpenSSF Package Analysis project, which flagged the package for communicating with a domain associated with malicious activities.

Using the compromised version can lead to data breaches, unauthorized access, and other security incidents, putting both the application and its users at risk.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file on the Vulert playground, you can determine if your application is affected without needing to sign up.

If you have used the compromised package, it is crucial to update to the latest secure version immediately and review your application for any potential security issues.

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 test-npm-style

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