Malicious Code Detected in gameai Package - Security Alert

gameai Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21168: Malicious code in gameai (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The gameai package is an npm library designed for game development, providing various functionalities to enhance game AI capabilities. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access or manipulation of data within affected systems.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the gameai package, which was introduced in version 0. This malicious code can compromise the integrity of applications using the package, potentially leading to data breaches, unauthorized access, or other malicious activities. Users of the package are at risk of exploitation if they do not take immediate action to mitigate this threat.

How To Fix

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

npm uninstall gameai

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 measure, you can avoid using the gameai package until a secure version is released. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the gameai package poses a serious threat to users and their applications. Immediate action is required to remove the package and seek alternatives. Regular monitoring of dependencies and utilizing tools like Vulert can help maintain security in your projects.

See every vulnerability recorded for gameai →

Share this vulnerability

FAQ

The gameai package is an npm library used for developing artificial intelligence in games, offering various tools and functionalities.

The specific nature of the malicious code has not been disclosed, but it poses significant security risks to applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

It is recommended to remove the gameai package from your project immediately and look for alternative solutions until a secure version is available.

As of now, there is no patched version available. Keep an eye on the package repository for updates.

How To Fix

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

npm uninstall gameai

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