Which versions of mrdaa-frontend are malicious?

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

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

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

If mrdaa-frontend was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is mrdaa-frontend part of a known attack campaign?

Yes — mrdaa-frontend is associated with the GHSA-r3r7-xhf7-xf87 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 mrdaa-frontend across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mrdaa-frontend (version 99.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mrdaa-frontend across your stack and pipelines.

Malicious package

mrdaa-frontendnpm

Malicious code in mrdaa-frontend (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3363

Immediate action

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

npm uninstall mrdaa-frontend

What this malware does

The package mrdaa-frontend was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'mrdaa-frontend' @ 99.2.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.2.1

Indicators of compromise (SHA-256)

ca0f1691dee1aebef2c443074b613ccf344f0af7812cc9a434b270649523ed6e

757aca74d8d75ecde7421f2c632969a5b34c11a279d9d28b75755c2ca0825ceb

0b6c586cd7adad52516658de8bbb3eb18f166350414f223fd73fe34a240d6948

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mrdaa-frontend (version 99.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mrdaa-frontend across your stack and pipelines.
If you installed it — respond
Remove mrdaa-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 mrdaa-frontend was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks mrdaa-frontend before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. mrdaa-frontend on npm has been identified as a malicious package (version 99.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r3r7-xhf7-xf87

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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