Malicious Code Detected in figcquery Package - Security Alert

figcquery Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20518: Malicious code in figcquery (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The figcquery package is an npm library designed for querying and manipulating data structures in JavaScript applications. It offers various functionalities that enhance data handling capabilities. However, recent investigations have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the figcquery package originates from the inclusion of malicious code that can compromise user data and application integrity. This code can lead to unauthorized access, data theft, or even complete system takeover. The malicious nature of this vulnerability makes it critical for developers to address it immediately to safeguard their applications.

How To Fix

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

npm uninstall figcquery

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 may consider removing the figcquery package from their project until a secure version is available. This can be achieved by executing the command: 'npm uninstall figcquery'.

Conclusion

The discovery of malicious code in the figcquery package highlights the importance of maintaining secure dependencies in software development. Users are strongly advised to update or remove the affected package to protect their applications from potential threats.

See every vulnerability recorded for figcquery →

Share this vulnerability

FAQ

figcquery is an npm package used for querying and manipulating data structures in JavaScript applications.

The malicious code can compromise user data and application integrity, potentially leading to unauthorized access and data theft.

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

As a temporary measure, you can uninstall the figcquery package from your project using the command 'npm uninstall figcquery'.

Utilizing tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time, ensuring you are alerted to any issues promptly.

How To Fix

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

npm uninstall figcquery

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