Which versions of whatsadmaidk are malicious?

The following npm versions of whatsadmaidk are flagged malicious: 1.1.2, 2.0.0. Treat any of these as compromised.

How do I remediate whatsadmaidk if I installed it?

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

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

Yes — whatsadmaidk is associated with the GHSA-h2gh-rhc4-98p2, IN-MAL-2026-010430, RLMA-2026-05652, RLUA-2026-06550 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 whatsadmaidk 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 whatsadmaidk (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging whatsadmaidk across your stack and pipelines.

Malicious package

whatsadmaidknpm

whatsadmaidk is a confirmed malicious npm package (MAL-2026-10396) that executes malicious code on install (malicious versions 1.1.2, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in whatsadmaidk (npm)

MAL-2026-10396

Immediate action

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

npm uninstall whatsadmaidk

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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

1.1.22.0.0

Indicators of compromise (SHA-256)

15d61e375712b5c2107876fd628d184370f3c6e85a5f6eae7bd832b476cd9377

604f59cbac58a8e35ba82016c72efe0c02226eec9273e96ee9215dd72cbe0392

18d1a67fb6387ef1232f4ad78dd64935488ed2afcd59760a1ca5f062de9785f3

282914d6e898540fd4c5be635512299329d531e7cf9fe7cdee8d455fc4c9a0b2

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

Campaign

GHSA-h2gh-rhc4-98p2IN-MAL-2026-010430RLMA-2026-05652RLUA-2026-06550

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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