Which versions of mx-frontend are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for mx-frontend (version 99.9.9).

Malicious package

mx-frontendnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

mx-frontend is a confirmed malicious npm package (MAL-2026-7325) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mx-frontend (npm)

MAL-2026-7325

Immediate action

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

npm uninstall mx-frontend

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

dd9dcdf2a2f4459411e5d916405b5f22e8481ddab376a9dfa1d9e07c203ddba0

f19b29c8b4ce464af0490eb1d2d87229f2af2c99ed2d8a96a3e874cf42796afa

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05170RLUA-2026-06338

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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