Critical Malicious Code Vulnerability in biclique Package

biclique Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15661: Malicious code in biclique (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 biclique package is an npm library designed for graph theory applications, particularly focusing on biclique structures within graphs. It is utilized by developers for efficient graph manipulation and analysis. However, the package has been found to contain malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the biclique package. This code can potentially compromise the integrity of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was identified in all versions starting from its introduction, making it critical for users to address it immediately.

How To Fix

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

npm uninstall biclique

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, users can remove the biclique package from their project until a secure version is released. This can be done using the command: 'npm uninstall biclique'. Alternatively, consider using a different package that provides similar functionality without the associated risks.

Conclusion

The biclique package has been identified as containing malicious code, which poses a significant risk to applications that utilize it. Users are strongly advised to update or remove the package to mitigate potential security threats. Monitoring tools like Vulert can assist in identifying vulnerabilities in real-time.

See every vulnerability recorded for biclique →

Share this vulnerability

FAQ

The biclique package is used for graph theory applications, specifically for manipulating and analyzing biclique structures in graphs.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without any signup.

If you cannot update the package right away, consider removing it from your project or using an alternative package until a secure version is released.

Using the compromised biclique package can lead to unauthorized access to your application, data breaches, and other malicious activities that could compromise your system's security.

The vulnerability was discovered by Amazon Inspector, a security service that helps identify vulnerabilities in applications.

How To Fix

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

npm uninstall biclique

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