Malicious Code Detected in Cavewars Package - Security Alert

cavewars Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16672: Malicious code in cavewars (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

Cavewars is an npm package designed for creating and managing interactive gaming experiences. It allows developers to build engaging game mechanics and user interfaces. However, recent findings have revealed that the package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the Cavewars package stems from the inclusion of malicious code that can compromise the security of applications using it. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall cavewars

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

As a temporary workaround, consider removing the Cavewars package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall cavewars'. This will prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The discovery of malicious code in the Cavewars package poses a serious threat to developers and users alike. Immediate action is required to mitigate risks, including updating or removing the package. Stay informed about updates and utilize tools like Vulert to monitor your applications for vulnerabilities.

See every vulnerability recorded for cavewars →

Share this vulnerability

FAQ

Cavewars is an npm package used for developing interactive gaming experiences, allowing developers to create engaging game mechanics.

The malicious code can lead to unauthorized access and data breaches, compromising the security of applications that use the package.

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

Currently, there is no patched version available. Users are advised to monitor the package repository for updates.

If immediate removal is not possible, ensure to limit the exposure of your application and monitor for any suspicious activity until a fix is available.

How To Fix

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

npm uninstall cavewars

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