Which versions of meta-internal-logger-drzak are malicious?

The following npm versions of meta-internal-logger-drzak are flagged malicious: 99.9.9, 99.13.0. Treat any of these as compromised.

How do I remediate meta-internal-logger-drzak if I installed it?

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

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

Yes — meta-internal-logger-drzak is associated with the GHSA-5m63-g4p4-w233, RLMA-2026-01786, RLUA-2026-01989 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 meta-internal-logger-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 meta-internal-logger-drzak (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging meta-internal-logger-drzak across your stack and pipelines.

Malicious package

meta-internal-logger-drzaknpm

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

MAL-2026-1398

Immediate action

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

npm uninstall meta-internal-logger-drzak

What this malware does

The package meta-internal-logger-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

2 flagged

99.9.999.13.0

Indicators of compromise (SHA-256)

fcc18756d586766d0270de654afe183d22e0592953dd084128043d085639d29c

1483f98fd78866cc6a27d31d99659bbb2912ec70d8771a004837f6fa46661a78

d1b944b75dadb33282ef0c55006e0f7415beeaf3cdc9322e9f728f0dd6f1f4cf

47ae1b7863f7ce972178fe3032196a90ac365081890a3ddb30cb39897f087ae2

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

Campaign

GHSA-5m63-g4p4-w233RLMA-2026-01786RLUA-2026-01989

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks meta-internal-logger-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