Which versions of fe-lib-singleton are malicious?

The following npm versions of fe-lib-singleton are flagged malicious: 99.99.9, 99.99.99, 999.999.999. Treat any of these as compromised.

How do I remediate fe-lib-singleton if I installed it?

Remove fe-lib-singleton from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed fe-lib-singleton — how do I know if it already compromised me?

If fe-lib-singleton was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is fe-lib-singleton part of a known attack campaign?

Yes — fe-lib-singleton is associated with the RLMA-2026-01315 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find fe-lib-singleton across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fe-lib-singleton (3 malicious versions).

Malicious package

fe-lib-singletonnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

fe-lib-singleton is a confirmed malicious npm package (MAL-2026-1736) that executes malicious code on install (malicious versions 99.99.9, 99.99.99, 999.999.999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fe-lib-singleton (npm)

MAL-2026-1736

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall fe-lib-singleton

What this malware does

The package fe-lib-singleton was found to contain malicious code.

Malicious versions

3 flagged

99.99.999.99.99999.999.999

Indicators of compromise (SHA-256)

c1b1a429ff418ebd40ea6ce280dd7039ef026c5c43d503831924b17addb5b4b0

96b6a629661c8cb3dd5aa39a16e1bd92ea60352ea95d0e0edc72e1aa3a59ad78

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for fe-lib-singleton (3 malicious versions).
If you installed it — respond
Remove fe-lib-singleton from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If fe-lib-singleton was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. fe-lib-singleton on npm has been identified as a malicious package (versions 99.99.9, 99.99.99, 999.999.999 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01315

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks fe-lib-singleton-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database