Malicious Code Detected in fooseapp Package - Security Alert

fooseapp Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20760: Malicious code in fooseapp (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 fooseapp package is an npm library designed for application development, providing various functionalities to streamline coding processes. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package. Users of fooseapp should be aware of its vulnerabilities and take necessary precautions.

Vulnerability Detail

The vulnerability in the fooseapp package originates from the inclusion of malicious code, which can compromise the security of applications that depend on it. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the application environment. The issue affects all versions starting from 0, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall fooseapp

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, consider removing the fooseapp package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall fooseapp'. This will prevent any potential exploitation from the malicious code present in the package.

Conclusion

The fooseapp package has been found to contain malicious code, posing serious security risks to applications. Users are advised to update or uninstall the package until a secure version is released. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for fooseapp →

Share this vulnerability

FAQ

fooseapp is an npm package used for application development, providing various functionalities to assist developers.

The malicious code can lead to unauthorized access and exploitation of applications that use the fooseapp 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.

As a workaround, you can uninstall the fooseapp package to prevent any potential security risks until a patched version is available.

Utilize tools like Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.

How To Fix

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

npm uninstall fooseapp

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