Malicious Code Detected in fig-echo-mango-puoow Package - Immediate Action Required

fig-echo-mango-puoow Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20458: Malicious code in fig-echo-mango-puoow (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-echo-mango-puoow package is an npm library designed for specific functionalities within JavaScript applications. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package. Users of this package should be aware of its potential vulnerabilities and take immediate action to safeguard their applications.

Vulnerability Detail

The vulnerability in the fig-echo-mango-puoow package arises from the presence of malicious code that can compromise the security of applications using it. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue originates from the package itself, which has been flagged for containing harmful scripts that can execute unwanted operations.

How To Fix

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

npm uninstall fig-echo-mango-puoow

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 prevent the execution of the malicious code by isolating the affected package or using a different package that provides similar functionality. However, the best course of action is to remove the package entirely.

Conclusion

The fig-echo-mango-puoow package has been flagged for containing malicious code that poses serious security risks. It is essential for developers to take immediate action by removing the package and monitoring their applications for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for fig-echo-mango-puoow →

Share this vulnerability

FAQ

It is an npm package used in JavaScript applications, but it has been found to contain malicious code.

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

Immediately remove the package from your project and update to a safer alternative or a patched version if available.

Using this package can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest versions.

How To Fix

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

npm uninstall fig-echo-mango-puoow

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