Critical Malicious Code Vulnerability in fe-lib-store Package

fe-lib-store Updated 02 Oct 2025

Summary

08/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5690: Malicious code in fe-lib-store (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 fe-lib-store package is an npm library designed for managing and storing frontend libraries in JavaScript applications. It is widely used for its ease of integration and functionality that allows developers to efficiently handle library dependencies. However, this package has been identified to contain malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the fe-lib-store package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code indicates that it may have been intentionally inserted to exploit users, leading to severe ramifications including data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall fe-lib-store

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, you can prevent the execution of the fe-lib-store package by removing it from your dependencies. Use the following command to uninstall it: npm uninstall fe-lib-store. Additionally, consider using alternative libraries that provide similar functionality without the associated risks.

Conclusion

The fe-lib-store package has been identified as containing malicious code that poses a significant security threat. Immediate action is required to remove the package and secure any potentially compromised information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for fe-lib-store →

Share this vulnerability

FAQ

Immediately uninstall the fe-lib-store package and rotate any secrets or keys that may have been compromised.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

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

Failure to address this vulnerability could lead to unauthorized access to sensitive data, system compromise, and potential data breaches.

It is advisable to review the security history and reputation of any package before use, especially if it has been associated with malicious activity.

How To Fix

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

npm uninstall fe-lib-store

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