Malicious Code Detected in Cheatmod Package - MAL-2025-16873

cheatmod Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16873: Malicious code in cheatmod (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 'cheatmod' package is an npm module designed for modifying game behavior, allowing users to implement cheats and enhancements in various games. While it offers unique functionalities for gamers, its recent discovery of malicious code poses significant risks to users, potentially compromising their systems and data.

Vulnerability Detail

The vulnerability in the 'cheatmod' package stems from the inclusion of malicious code that can execute harmful actions on users' systems. This code was introduced in version 0 and can lead to unauthorized access, data theft, or system compromise. Users of this package are at risk of severe ramifications, including loss of sensitive information and potential exploitation by malicious actors.

How To Fix

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

npm uninstall cheatmod

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, users can remove the 'cheatmod' package from their projects until a secure version is released. This can be done using the command: 'npm uninstall cheatmod'.

Conclusion

The discovery of malicious code in the 'cheatmod' package highlights the importance of vigilance when using open-source software. Users are advised to take immediate action by updating or removing the package to safeguard their systems. Regular monitoring of dependencies is essential to prevent future vulnerabilities.

See every vulnerability recorded for cheatmod →

Share this vulnerability

FAQ

The malicious code can execute harmful actions on the user's system, potentially leading to data theft or unauthorized access.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If you have installed cheatmod, it is crucial to uninstall it immediately and check for any updates or patches from the package maintainers.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation by attackers.

Utilizing tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time, ensuring you are alerted to any issues promptly.

How To Fix

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

npm uninstall cheatmod

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