Which versions of debug-mj are malicious?

The following npm versions of debug-mj are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate debug-mj if I installed it?

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

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

Yes — debug-mj is associated with the GHSA-53wf-4p29-6x4w, RLMA-2025-05719 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 debug-mj 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 debug-mj (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging debug-mj across your stack and pipelines.

Malicious package

debug-mjnpm

debug-mj is a confirmed malicious npm package (MAL-2025-48429) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in debug-mj (npm)

MAL-2025-48429

Immediate action

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

npm uninstall debug-mj

What this malware does

The package communicates with a domain associated with malicious activity.

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

9f60289f1a0f9296cf8aa9ed744c256c0963a95dc751ff52a708d2676d14825a

bc51786929872e6224fa65be01fdb3c446a024c1292b256731640a741547c31d

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 debug-mj (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging debug-mj across your stack and pipelines.
If you installed it — respond
Remove debug-mj 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 debug-mj 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 debug-mj 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. debug-mj on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-53wf-4p29-6x4wRLMA-2025-05719

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks debug-mj-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