Which versions of fusion-internal-common-drzak are malicious?

The following npm versions of fusion-internal-common-drzak are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate fusion-internal-common-drzak if I installed it?

Remove fusion-internal-common-drzak 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 fusion-internal-common-drzak — how do I know if it already compromised me?

If fusion-internal-common-drzak 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 fusion-internal-common-drzak part of a known attack campaign?

Yes — fusion-internal-common-drzak is associated with the GHSA-84r2-9pxx-jpj2, RLMA-2026-01765, RLUA-2026-01951 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 fusion-internal-common-drzak 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 fusion-internal-common-drzak (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fusion-internal-common-drzak across your stack and pipelines.

Malicious package

fusion-internal-common-drzaknpm

Malicious code in fusion-internal-common-drzak (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1397

Immediate action

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

npm uninstall fusion-internal-common-drzak

What this malware does

The package fusion-internal-common-drzak 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.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

6f5ed73ca3b3481adf9ebf13e7be64bae319ca28e2fc3bb1da8e3534ac4fbaa8

3a185377a78b169ac6bc30d82d4ba1031a1a2b7024e15a17ae5a2df8bc8fefc2

b7f34f0af7f7cb7caf9d8c5fd9cd670f3d7cac2244d4e3141992b45a7b020fd0

252432b9a35f2eff00c11569d1c1932f9c092dc981ff1afbc984c9ff4bd9b483

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 fusion-internal-common-drzak (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fusion-internal-common-drzak across your stack and pipelines.
If you installed it — respond
Remove fusion-internal-common-drzak 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 fusion-internal-common-drzak 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 fusion-internal-common-drzak 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. fusion-internal-common-drzak 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

GHSA-84r2-9pxx-jpj2RLMA-2026-01765RLUA-2026-01951

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks fusion-internal-common-drzak-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