Which versions of notepad-monorepo are malicious?

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

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

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

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

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

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

Malicious package

notepad-monoreponpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7329

Immediate action

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

npm uninstall notepad-monorepo

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

955d7942f4767d1ed32b107186aa9a42738c4eba5df3eb5a2a2aca5d4682bfee

21accbfe71a91de028c2be50dce9f27e97003174081ebc51f4b98a7300f45e05

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks notepad-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