Malicious Code Detected in fe-app-inbox Package - Security Alert

fe-app-inbox Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20335: Malicious code in fe-app-inbox (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The fe-app-inbox package is an npm library designed for managing inbox functionalities in web applications. It provides features such as message retrieval, notification handling, and user interaction capabilities. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability in the fe-app-inbox package stems from the inclusion of malicious code that can compromise user data and application integrity. This code may allow unauthorized access to sensitive information or facilitate further attacks on the system. The issue originated from the package's source code, which was found to be tampered with, leading to potential exploitation by malicious actors.

How To Fix

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

npm uninstall fe-app-inbox

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

If immediate updating is not feasible, consider removing the fe-app-inbox package from your project until a secure version is released. You can do this by executing: npm uninstall fe-app-inbox. Additionally, review your application for any dependencies that may rely on this package and assess their security.

Conclusion

The discovery of malicious code in the fe-app-inbox package highlights the importance of regularly auditing and updating dependencies in software projects. By taking proactive measures, such as updating to secure versions and utilizing monitoring tools like Vulert, developers can safeguard their applications against potential threats.

See every vulnerability recorded for fe-app-inbox →

Share this vulnerability

FAQ

The fe-app-inbox package is an npm library used for managing inbox functionalities in web applications, including message handling and notifications.

The malicious code was identified through security audits and monitoring tools, which flagged the package for containing harmful scripts.

Using the compromised fe-app-inbox package can lead to unauthorized access to user data, potential data breaches, and exploitation of application vulnerabilities.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

If an immediate update is not possible, consider removing the package from your project and reviewing any dependent packages for security risks.

How To Fix

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

npm uninstall fe-app-inbox

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