Critical Malicious Code Vulnerability in viktorparserctf2 Package

viktorparserctf2 Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192648: Malicious code in viktorparserctf2 (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The viktorparserctf2 package is an npm library designed for parsing data in Capture The Flag (CTF) competitions. It is widely used by developers to streamline the process of handling CTF-related data. However, this package has been found to contain malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the viktorparserctf2 package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it may lead to data breaches and loss of control over the affected systems. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall viktorparserctf2

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. The only recommended action is to uninstall the package and secure any sensitive information.

Conclusion

The viktorparserctf2 package contains malicious code that poses a significant security risk to any system where it is installed. Immediate action is required to uninstall the package and secure sensitive information. Users should remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for viktorparserctf2 →

Share this vulnerability

FAQ

You should immediately uninstall the viktorparserctf2 package and rotate any sensitive information stored on the affected system.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without any signup.

No, there is currently no patched version available for the viktorparserctf2 package. The only solution is to uninstall it.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your systems.

No, it is highly recommended to avoid using viktorparserctf2 due to the embedded malicious code that compromises system security.

How To Fix

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

npm uninstall viktorparserctf2

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