Which versions of fnnote-combined are malicious?

The following npm versions of fnnote-combined are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate fnnote-combined if I installed it?

Remove fnnote-combined 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 fnnote-combined — how do I know if it already compromised me?

If fnnote-combined 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 fnnote-combined part of a known attack campaign?

Yes — fnnote-combined is associated with the RLMA-2026-05093, RLUA-2026-06246 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 fnnote-combined across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fnnote-combined (version 99.99.99).

Malicious package

fnnote-combinednpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

fnnote-combined is a confirmed malicious npm package (MAL-2026-7288) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fnnote-combined (npm)

MAL-2026-7288

Immediate action

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

npm uninstall fnnote-combined

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

c028544bb66a4b1eb428051471f04a47a0ee8175300fcfcf91ecedbbe6050df4

15979f7f98b830cabef3b7b42416c213523eabd99ea636f2e7366f022029b8e8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for fnnote-combined (version 99.99.99).
If you installed it — respond
Remove fnnote-combined 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 fnnote-combined 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. fnnote-combined on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05093RLUA-2026-06246

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks fnnote-combined-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