Which versions of fnnote-frontend are malicious?

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

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

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

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

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

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

Malicious package

fnnote-frontendnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

fnnote-frontend is a confirmed malicious npm package (MAL-2026-7289) 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-frontend (npm)

MAL-2026-7289

Immediate action

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

npm uninstall fnnote-frontend

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

23b8c648c20e400e0411777628b6990aa826a7c3a8eea1d3d199af690f712698

44673bc644028d9c30bb6bf99742103ac883d3096b9f1b5fbc2689a3e3ab91da

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for fnnote-frontend (version 99.99.99).
If you installed it — respond
Remove fnnote-frontend 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-frontend 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-frontend 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-05094RLUA-2026-06247

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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