Critical Malicious Code Vulnerability in viktorparserctf8 Package

viktorparserctf8 Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192654: Malicious code in viktorparserctf8 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The viktorparserctf8 package is an npm library that is utilized for parsing data in Capture The Flag (CTF) competitions. It is designed to facilitate the handling of various data formats commonly used in these events. However, this package has been identified to contain malicious code that poses a significant security risk to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the viktorparserctf8 package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to complete system takeover by an external entity. Users are advised to treat any system with this package installed as fully compromised.

How To Fix

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

npm uninstall viktorparserctf8

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 other than removing the package and securing the system. Ensure that you monitor your system for any signs of compromise and take necessary actions to secure it.

Conclusion

The viktorparserctf8 package contains a critical vulnerability due to embedded malicious code. Users must act swiftly to remove the package and secure their systems to prevent unauthorized access. Continuous monitoring for vulnerabilities is essential to maintain system integrity.

See every vulnerability recorded for viktorparserctf8 →

Share this vulnerability

FAQ

The viktorparserctf8 package is an npm library used for parsing data in Capture The Flag competitions.

The malicious code can lead to complete system compromise, allowing unauthorized access to sensitive information.

Immediately remove the viktorparserctf8 package and rotate any secrets or keys stored on the affected system.

Currently, there is no patched version available. Users should focus on removing the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json. Check your application using the Vulert playground at Vulert Scanner.

How To Fix

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

npm uninstall viktorparserctf8

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.