Malicious Code Detected in security-testing-research22 Package - Version 1.1.9
Summary
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 ↓
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.
No signup required · Results in about 60 seconds
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 →
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.