Which versions of playwright-atoned are malicious?

The following PyPI versions of playwright-atoned are flagged malicious: 0.1.0, 1.1.0, 1.2.0, 1.3.0. Treat any of these as compromised.

How do I remediate playwright-atoned if I installed it?

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

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

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

Malicious package

playwright-atonedPyPI

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

MAL-2026-3355

Immediate action

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

pip uninstall playwright-atoned

What this malware does

The package exfiltrates sensitive data like local environmental variables and cloud tokens

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

Campaign: 2026-05-playwright-acustomed

Reasons (based on the campaign):

exfiltration-cloud-tokens
exfiltration-env-variables
exfiltration-generic
clones-real-package

Malicious versions

4 flagged

0.1.01.1.01.2.01.3.0

Indicators of compromise (SHA-256)

250795bc04569c6f87e372e4b6bed019148a1c78f4357e8e430c1865acfead07

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

Campaign

2026-05-playwright-acustomed

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks playwright-atoned-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