Which versions of agdebugger-frontend are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for agdebugger-frontend (version 0.0.1).

Malicious package

agdebugger-frontendnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

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

Malicious code in agdebugger-frontend (npm)

MAL-2026-2724

Immediate action

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

npm uninstall agdebugger-frontend

What this malware does

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

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f626b219ae2569fbc3d0448a3ebcaf326b13837c61ef1147afa7c65e991cade4

be34269bebfc9203228b56604d750ac51bdf4f84cbf58141d3317fc45c8854ad

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01880

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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