Which versions of notepad-frontend are malicious?

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

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

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

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

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

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

Malicious package

notepad-frontendnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7328

Immediate action

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

npm uninstall notepad-frontend

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

6d7de28ed2786d52e3c8cda89ca402e1887d0b4646168fc2dc0c74af98af14b0

240dceab0de64a6f3d581b436706958418e960b98edf69944d48eb18af03f7a7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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