Which versions of whoisbuild are malicious?

The following PyPI versions of whoisbuild are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate whoisbuild if I installed it?

whoisbuild is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed whoisbuild — how do I know if it already compromised me?

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

Yes — whoisbuild is associated with the duvet-love-odyssey 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 whoisbuild 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 whoisbuild (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging whoisbuild across your stack and pipelines.

Malicious package

whoisbuildPyPI

Malicious code in whoisbuild (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12370

Immediate action

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

pip uninstall whoisbuild

What this malware does

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: duvet-love-odyssey

Reasons (based on the campaign):

infostealer

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

535cd9dcf328b0ef7aa2f1e58cf9f55656d5fcf8a4595f07384f10befb674927

b8f206b101a7dd5ada26eac1215351711e553298254e775f02bf41b15b6b55b7

37be6fc8dcdf96c35d28827fd80a5b6ce14c3ce53bc25edb69b65b7d2835d8ce

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for whoisbuild (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging whoisbuild across your stack and pipelines.
If you installed it — respond
whoisbuild is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If whoisbuild 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 whoisbuild 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. whoisbuild on PyPI has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

duvet-love-odyssey

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks whoisbuild-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring