Malicious Code Detected in fig-t1g-project Package

fig-t1g-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20501: Malicious code in fig-t1g-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The fig-t1g-project package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers to enhance their projects with additional features. However, this package has been found to contain malicious code, posing a significant security risk to applications that depend on it.

Vulnerability Detail

The vulnerability in the fig-t1g-project package originates from the inclusion of malicious code that can compromise the integrity and security of applications using this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The vulnerability is present in all versions starting from its introduction, making it critical for users to take immediate action.

How To Fix

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

npm uninstall fig-t1g-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 workaround, consider removing the fig-t1g-project package from your project until a secure version is released. You can do this by executing: npm uninstall fig-t1g-project.

Conclusion

The fig-t1g-project package has been identified as containing malicious code, posing a serious risk to applications that utilize it. Immediate action is required to update or remove the package to safeguard your projects. Utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for fig-t1g-project →

Share this vulnerability

FAQ

The fig-t1g-project package is an npm library used in JavaScript applications to provide additional functionalities.

The malicious code can lead to unauthorized access and potential data breaches within applications that utilize the fig-t1g-project package.

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.

Users are encouraged to check the package repository for any patched versions of fig-t1g-project that address this vulnerability.

As a temporary measure, you can uninstall the fig-t1g-project package from your project until a secure version is available.

How To Fix

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

npm uninstall fig-t1g-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