Malicious Code Detected in Gamestore Package - Security Alert

gamestore Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21175: Malicious code in gamestore (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 'gamestore' package is an npm library designed for managing game-related functionalities within applications. It provides developers with tools to integrate gaming features seamlessly. However, it has been identified to contain malicious code, posing significant security risks to applications utilizing this package.

Vulnerability Detail

The vulnerability in the 'gamestore' package stems from the inclusion of malicious code that can compromise the security of applications that depend on it. 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 take immediate action.

How To Fix

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

npm uninstall gamestore

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 remove the 'gamestore' package from your project until a secure version is released. Use the following command to uninstall it: 'npm uninstall gamestore'. This will prevent any potential exploitation of the malicious code.

Conclusion

The discovery of malicious code in the 'gamestore' package highlights the importance of maintaining secure dependencies in software development. Immediate action is required to mitigate risks associated with this vulnerability. Regular monitoring and updates are essential to ensure the security of your applications.

See every vulnerability recorded for gamestore →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If an immediate update is not possible, consider removing the package from your project as a temporary workaround.

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

You can find more information about the gamestore package on its official npm page or GitHub repository.

How To Fix

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

npm uninstall gamestore

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