Malicious Code Detected in bilard Package - Security Alert

bilard Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15681: Malicious code in bilard (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 bilard package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various purposes, including game development and interactive applications. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the bilard package, which was introduced in version 0. This code can compromise the security of applications that utilize bilard, potentially leading to unauthorized access, data breaches, or other malicious activities. Users of this package are at risk of exploitation due to this vulnerability, making it imperative to address the issue promptly.

How To Fix

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

npm uninstall bilard

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, consider removing the bilard package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall bilard'. This will help prevent any potential exploitation while waiting for a fix.

Conclusion

The bilard package has been identified to contain malicious code, posing a significant security risk to users. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can help monitor vulnerabilities effectively.

See every vulnerability recorded for bilard →

Share this vulnerability

FAQ

bilard is an npm package used for various functionalities in JavaScript applications, including game development.

The malicious code can compromise application security, leading to unauthorized access and potential data breaches.

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

Currently, there is no specific patch version mentioned, but users are advised to update to the latest version when available.

As a workaround, consider uninstalling the bilard package until a secure version is released to prevent any exploitation.

How To Fix

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

npm uninstall bilard

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