Critical Malicious Code Vulnerability in fe-lib-sequences Package

fe-lib-sequences Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1735: Malicious code in fe-lib-sequences (npm). Affects fe-lib-sequences versions 99.99.9 – 999.999.999. 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 fe-lib-sequences package is a JavaScript library available on npm that is used for handling sequences in various applications. It is designed to provide developers with a set of tools to manage and manipulate sequences efficiently. However, this package has been identified to contain malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the fe-lib-sequences package arises from the inclusion of malicious code that can compromise the integrity of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue was reported by ReversingLabs and affects specific versions of the package, including 99.99.9, 99.99.99, and 999.999.999. Users of these versions are at risk and should take immediate action to mitigate potential threats.

How To Fix

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

npm uninstall fe-lib-sequences

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-lib-sequences package from your project until a secure version is available. You can do this by running: npm uninstall fe-lib-sequences. Additionally, monitor your application for any unusual behavior that may indicate exploitation of this vulnerability.

Conclusion

The fe-lib-sequences package has a critical vulnerability due to the presence of malicious code. It is essential for developers using this package to take immediate action by updating to a secure version or removing the package altogether. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for fe-lib-sequences →

Share this vulnerability

FAQ

fe-lib-sequences is a JavaScript library used for managing sequences in applications, available through npm.

The malicious code can lead to unauthorized access and data breaches, compromising the security of applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Consider removing the fe-lib-sequences package from your project and monitor for any unusual application behavior until a secure version is available.

The vulnerability was reported by ReversingLabs, a security research organization.

How To Fix

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

npm uninstall fe-lib-sequences

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