Malicious Code Detected in fig-o37-project Package - Security Alert

fig-o37-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20491: Malicious code in fig-o37-project (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 fig-o37-project is an npm package designed for developers to facilitate specific functionalities within their applications. It is commonly used for its ease of integration and user-friendly interface. However, recent findings have revealed that this package contains malicious code, posing a significant risk to users who have integrated it into their projects.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the fig-o37-project package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was identified by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security vulnerabilities.

How To Fix

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

npm uninstall fig-o37-project

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 avoid using the fig-o37-project package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider implementing security measures such as code reviews and dependency audits to mitigate potential threats.

Conclusion

The discovery of malicious code in the fig-o37-project package serves as a reminder of the importance of scrutinizing third-party dependencies. Users are advised to take immediate action to remove the affected package and consider alternative solutions to safeguard their applications.

See every vulnerability recorded for fig-o37-project →

Share this vulnerability

FAQ

The fig-o37-project is an npm package used by developers to enhance their applications with specific functionalities.

The malicious code found in the fig-o37-project package can lead 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 if your application is affected without any signup.

If you have used the fig-o37-project package, it is crucial to remove it immediately and look for alternative solutions.

Implementing regular code reviews, dependency audits, and using tools like Vulert can help identify and mitigate vulnerabilities in your projects.

How To Fix

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

npm uninstall fig-o37-project

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