Critical Malicious Code Vulnerability in gaaaaaam Package

gaaaaaam Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21104: Malicious code in gaaaaaam (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The gaaaaaam package is an npm library designed for specific functionalities within JavaScript applications. It is widely used due to its ease of integration and utility in various projects. However, it has been identified to contain malicious code that poses significant security risks to applications relying on it.

Vulnerability Detail

The vulnerability in the gaaaaaam package stems from the inclusion of malicious code that can compromise the integrity of applications using this library. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall gaaaaaam

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 isolate the gaaaaaam package in a separate environment to limit its impact while searching for a secure alternative. Additionally, consider using dependency management tools to monitor and manage package vulnerabilities.

Conclusion

The gaaaaaam package has been identified as containing malicious code, posing serious security risks to applications. Immediate action is required to remove the package and replace it with a secure alternative. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for gaaaaaam →

Share this vulnerability

FAQ

The gaaaaaam package is an npm library used for various functionalities in JavaScript applications, but it has been compromised with malicious code.

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

You should remove the gaaaaaam package from your project immediately and replace it with a secure alternative.

Currently, there is no patched version available for the gaaaaaam package, so removal is necessary.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall gaaaaaam

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