Malicious Code Detected in security-testing-research22 Package - Version 1.1.9

security-testing-research22 Updated 21 Nov 2025

Summary

18/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190567: Malicious code in security-testing-research22 (npm). Affects security-testing-research22 versions 1.1.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 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 'security-testing-research22' package is an npm library designed for security testing and research purposes. It is utilized by developers to facilitate various security assessments. However, version 1.1.9 has been flagged for malicious behavior, making it a significant concern for users relying on its functionality.

Vulnerability Detail

The vulnerability originates from the package's ability to communicate with a domain linked to malicious activities. Additionally, it executes commands that are associated with harmful behavior, potentially compromising the security of systems that utilize this package. This could lead to unauthorized access, data breaches, or other malicious outcomes.

How To Fix

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

npm uninstall security-testing-research22

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, users can avoid using the 'security-testing-research22' package altogether until a secure version is released. Consider using other security testing libraries that do not exhibit malicious behavior.

Conclusion

The 'security-testing-research22' package version 1.1.9 has been identified as malicious, posing significant risks to users. It is crucial to remove this version and seek alternatives to ensure the security of your applications. Regular monitoring of dependencies using tools like Vulert can help maintain a secure development environment.

See every vulnerability recorded for security-testing-research22 →

Share this vulnerability

FAQ

The package communicates with a domain known for malicious activities and executes harmful commands.

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

If no patched version is available, consider removing the package and using alternative libraries that provide similar functionality.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring you stay informed about potential risks.

No, it is not safe to use version 1.1.9 as it has been identified as malicious. It is recommended to remove it immediately.

How To Fix

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

npm uninstall security-testing-research22

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