Critical Malicious Code Vulnerability in viktorparserctf9 Package

viktorparserctf9 Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192655: Malicious code in viktorparserctf9 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The viktorparserctf9 package is an npm library designed for parsing and handling data in various formats. It is often utilized in applications that require data manipulation and processing. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the viktorparserctf9 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 control of the affected computer 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 viktorparserctf9

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 best course of action is to uninstall the package and secure your system.

Conclusion

The viktorparserctf9 package has been identified as containing malicious code that poses a significant security threat. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring of dependencies is essential to prevent similar vulnerabilities in the future.

See every vulnerability recorded for viktorparserctf9 →

Share this vulnerability

FAQ

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

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

Leaving this package installed can lead to unauthorized access to your system, data breaches, and potential control by malicious actors.

Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Vulert is a service that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall viktorparserctf9

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