Malicious Code Detected in fig-orange-vxjw: A Critical npm Vulnerability

fig-orange-vxjw Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20493: Malicious code in fig-orange-vxjw (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 package fig-orange-vxjw is an npm package that is used for various functionalities in JavaScript applications. It is designed to facilitate specific tasks within the npm ecosystem. However, this package has been identified to contain malicious code, posing a significant risk to applications that depend on it. Users of this package should be aware of its potential to compromise application security.

Vulnerability Detail

The vulnerability in fig-orange-vxjw stems from the inclusion of malicious code within the package. This code can lead to unauthorized access, data breaches, or other harmful actions within the applications that utilize this package. The issue was introduced from version 0 and affects all subsequent versions. The ramifications of this vulnerability can be severe, potentially leading to loss of sensitive data or control over the affected systems.

How To Fix

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

npm uninstall fig-orange-vxjw

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, you can replace the functionality provided by fig-orange-vxjw with an alternative package that does not have known vulnerabilities. Ensure to review the alternatives thoroughly before implementation.

Conclusion

The discovery of malicious code in the fig-orange-vxjw npm package presents a serious security threat to applications using it. Users are advised to uninstall the package and seek alternatives to safeguard their applications. Continuous monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for fig-orange-vxjw →

Share this vulnerability

FAQ

fig-orange-vxjw is an npm package used in JavaScript applications for specific functionalities.

The vulnerability involves malicious code that can compromise application security.

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

It is recommended to uninstall the fig-orange-vxjw package immediately and look for alternative packages.

Currently, there is no patched version available. The best course of action is to remove the package.

How To Fix

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

npm uninstall fig-orange-vxjw

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