Malicious Code Detected in beyblade Package - Security Alert

beyblade Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15628: Malicious code in beyblade (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 beyblade package is an npm library designed for building and managing game mechanics. It offers various functionalities that allow developers to create engaging experiences. However, this package has been flagged for containing malicious code, which poses a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the beyblade package stems from the presence of malicious code that can compromise the security of applications using this library. This code may 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 address this vulnerability promptly.

How To Fix

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

npm uninstall beyblade

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 beyblade package from your project until a secure version is released. You can do this by executing the following command: npm uninstall beyblade. This will help mitigate the risk associated with the malicious code until a fix is provided.

Conclusion

The beyblade package has been identified as containing malicious code, which poses significant security risks. Users are advised to update the package as soon as a patched version is released or to uninstall it temporarily to protect their applications. Monitoring tools like Vulert can assist in identifying vulnerabilities in real-time.

See every vulnerability recorded for beyblade →

Share this vulnerability

FAQ

The beyblade package is an npm library used for creating game mechanics and managing gameplay elements.

The malicious code can lead to unauthorized access and potential data breaches within applications using the beyblade 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.

As of now, a patched version has not been released. Users should monitor the package repository for updates.

If an immediate update is not possible, consider uninstalling the beyblade package to mitigate risks until a secure version is available.

How To Fix

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

npm uninstall beyblade

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