Which versions of mysql-dumpdiscord are malicious?

The following npm versions of mysql-dumpdiscord are flagged malicious: 1.0.0, 1.0.2, 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate mysql-dumpdiscord if I installed it?

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

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

Yes — mysql-dumpdiscord is associated with the GHSA-p8c4-9q6r-g4m6, RLMA-2025-05076, RLUA-2026-01438 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 mysql-dumpdiscord 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 mysql-dumpdiscord (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mysql-dumpdiscord across your stack and pipelines.

Malicious package

mysql-dumpdiscordnpm

mysql-dumpdiscord is a confirmed malicious npm package (MAL-2025-47191) that executes malicious code on install (malicious versions 1.0.0, 1.0.2, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mysql-dumpdiscord (npm)

MAL-2025-47191

Immediate action

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

npm uninstall mysql-dumpdiscord

What this malware does

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

4 flagged

1.0.01.0.21.0.31.0.4

Indicators of compromise (SHA-256)

a71ef5bb0add3bd32fba8e827c6a43a6d7889f8a640286196a4a3057be865e1b

ce57674f41e538e7155e6df85dfa30341e24587a04efd78d659b9cc6bd168dfc

4c1084dd245c92b0391327dd324b0b53ee8067ca88b5497192c307db95c00b18

e1fbb6cf3f3dbcb965a12f217abf7d003f066eaa2ef20438176c898ac2142fd5

d483ce3d559b46e3efbaa91e8a1b1f7e14c215b852980f7d7f3d3cc46b8f395c

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

Campaign

GHSA-p8c4-9q6r-g4m6RLMA-2025-05076RLUA-2026-01438

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks mysql-dumpdiscord-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