Malicious Code Vulnerability in testctfproject2 Package

testctfproject2 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1865: Malicious code in testctfproject2 (npm). Affects testctfproject2 versions 0.30.1 – 1.0.0. 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 testctfproject2 package is an npm module designed for testing purposes in CTF (Capture The Flag) competitions. It provides various tools and functionalities to facilitate the creation and management of CTF challenges. However, this package has been identified to contain malicious code that can compromise the security of applications utilizing it.

Vulnerability Detail

The vulnerability arises from the inclusion of malicious code within the testctfproject2 package. This code can potentially execute harmful actions on the host system, leading to unauthorized access, data breaches, or other malicious activities. The malicious code was discovered in versions 0.30.1 and 1.0.0, and it poses a significant risk to any application that relies on this package.

How To Fix

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

npm uninstall testctfproject2

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

If immediate updating is not feasible, consider removing the testctfproject2 package from your project until a secure version is released. You can do this by running: npm uninstall testctfproject2.

Conclusion

The testctfproject2 package has been identified to contain malicious code that poses a significant security risk. It is crucial for developers to update to a patched version or remove the package entirely to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for testctfproject2 →

Share this vulnerability

FAQ

The malicious code can execute unauthorized actions on the host system, leading to potential data breaches and security vulnerabilities.

Versions 0.30.1 and 1.0.0 of the testctfproject2 package are known to contain the malicious code.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can provide real-time alerts for any vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you cannot update the package right away, it is advisable to remove the testctfproject2 package from your project until a secure version is available.

How To Fix

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

npm uninstall testctfproject2

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