Critical Malicious Code Vulnerability in ctfvampir Package

ctfvampir Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192667: Malicious code in ctfvampir (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

ctfvampir is an npm package designed for specific functionalities within the Node.js ecosystem. It is utilized by developers for various tasks, but its recent exposure to malicious code has raised significant concerns. The package's functionality may include handling data or interacting with other services, making it a potential target for exploitation. Users of ctfvampir should be aware of its vulnerabilities and the implications of using compromised packages.

Vulnerability Detail

The ctfvampir package has been identified as containing malicious code, which poses a severe risk to any system where it is installed. This vulnerability originates from a malicious actor who embedded harmful code within the package, leading to full compromise of the affected systems. Users are advised to treat any computer with this package installed as fully compromised, as sensitive information such as secrets and keys may be exposed. The malicious code can allow unauthorized access and control over the affected systems, making it imperative for users to act swiftly.

How To Fix

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

npm uninstall ctfvampir

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. Users should ensure that they have removed all traces of the ctfvampir package and any associated malicious software.

Conclusion

The ctfvampir package has been compromised with malicious code, posing a significant risk to users. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for ctfvampir →

Share this vulnerability

FAQ

You should immediately remove the ctfvampir package and rotate any sensitive information stored on your system.

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

Currently, there is no patch available. The best course of action is to remove the package entirely.

Failing to address this vulnerability can lead to unauthorized access, data breaches, and potential control over your system by malicious actors.

Vulert monitors and alerts users in real-time for open-source vulnerabilities using just the package-lock.json file, providing an easy way to stay informed.

How To Fix

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

npm uninstall ctfvampir

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