Which versions of buildpeople are malicious?

The following PyPI versions of buildpeople are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate buildpeople if I installed it?

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

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

Yes — buildpeople is associated with the RLMA-2025-04750, 2025-08-k7eel, RLUA-2026-00160 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 buildpeople 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 buildpeople (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging buildpeople across your stack and pipelines.

Malicious package

buildpeoplePyPI

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

MAL-2025-47751

Immediate action

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

pip uninstall buildpeople

What this malware does

Importing the module downloads and executes widely recognized malware

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

Campaign: 2025-08-k7eel

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

b2e8248acb69b6c38b76cbf3a74ba5bdbe8d0e76baca13b967ccd09a5e7de84a

441d4ab001733d403a34676acd61693289a830cadb0901fa136d6cbd0821dd8f

a66da54489a807c99f01a12ccc490a7111f8929f15b2f28d3a1c9a1cc07c1563

aa780b318d8cde2486da2ed30736907f582ec22214b344a80d08f27a13467efa

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

Campaign

RLMA-2025-047502025-08-k7eelRLUA-2026-00160

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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