Which versions of fnnote-monorepo are malicious?

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

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

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

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

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

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

Malicious package

fnnote-monoreponpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7290

Immediate action

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

npm uninstall fnnote-monorepo

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

631c9e485274430283593e84f1019415feff7a9077e046e0371748ff8d50c127

c09a54ba75ceda5c4a270c93115c90af9485f20645ad6a9d3c652826a918a641

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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