Malicious Code Detected in fig-cherry-yejf: A Critical npm Vulnerability

fig-cherry-yejf Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20455: Malicious code in fig-cherry-yejf (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 package fig-cherry-yejf is an npm package that has been identified to contain malicious code. npm, or Node Package Manager, is a widely used package manager for JavaScript, allowing developers to share and reuse code. The fig-cherry-yejf package, like many others, is intended to facilitate specific functionalities within JavaScript applications. However, the presence of malicious code poses significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the fig-cherry-yejf package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code could lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it imperative for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall fig-cherry-yejf

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 can avoid using the fig-cherry-yejf package until a secure version is released. Additionally, monitoring tools like Vulert can be employed to keep track of vulnerabilities in your project. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The fig-cherry-yejf package has been identified as containing malicious code, which poses significant risks to applications that utilize it. Users are advised to take immediate action by removing or updating the package and utilizing tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for fig-cherry-yejf →

Share this vulnerability

FAQ

fig-cherry-yejf is an npm package that has been found to contain malicious code, posing security risks to applications that use it.

The malicious code can lead to unauthorized access, data breaches, and other harmful actions within your application.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

You should remove the fig-cherry-yejf package or update it to a patched version if available. Consider replacing it with a secure alternative.

Vulert is a monitoring tool that uses package-lock.json to alert users in real-time about open-source vulnerabilities in their software.

How To Fix

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

npm uninstall fig-cherry-yejf

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