Which versions of paperclip-ai are malicious?

The following PyPI versions of paperclip-ai are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate paperclip-ai if I installed it?

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

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

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

Malicious package

paperclip-aiPyPI

Malicious code in paperclip-ai (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-10869

Immediate action

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

pip uninstall paperclip-ai

What this malware does

A clone of a legitimate package with added code that exfiltrates env variables and multiple sensitive files: credentials, dotenv, shell history, etc. Exfiltrated credentials were quickly validated by the attacker.

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

Campaign: 2026-07-browser-use-headless

Reasons (based on the campaign):

files-exfiltration
exfiltration-env-variables
exfiltration-credentials
clones-real-package

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

643de4cab1ea2f7becbca5a7dead46fcb39f35596d2bf7a371fdd2c82ded1530

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

Campaign

2026-07-browser-use-headless

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks paperclip-ai-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