Critical Malicious Code Vulnerability in viktorparserctf4 Package

viktorparserctf4 Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192650: Malicious code in viktorparserctf4 (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 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 viktorparserctf4 package is an npm library designed for parsing data in Capture The Flag (CTF) competitions. It is utilized by developers to streamline the process of handling CTF data formats. However, this package has been identified as containing malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the viktorparserctf4 package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that any computer running this package should be considered fully compromised, and the risk extends beyond mere data theft to potential complete control by external entities.

How To Fix

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

npm uninstall viktorparserctf4

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 the system.

Conclusion

The discovery of malicious code within the viktorparserctf4 package highlights the importance of vigilance in managing open-source dependencies. Immediate action is required to mitigate risks associated with this vulnerability, including the uninstallation of the package and the rotation of sensitive information.

See every vulnerability recorded for viktorparserctf4 →

Share this vulnerability

FAQ

You should uninstall the viktorparserctf4 package immediately and rotate any sensitive information stored on your system.

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

Leaving the viktorparserctf4 package installed can lead to unauthorized access to your system and potential data breaches.

After uninstalling the package, you should rotate all secrets and keys and monitor your system for any unusual activity.

While many npm packages are safe, it's essential to review and monitor all dependencies for vulnerabilities regularly.

How To Fix

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

npm uninstall viktorparserctf4

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