Which versions of chrome-stealth are malicious?

The following PyPI versions of chrome-stealth are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate chrome-stealth if I installed it?

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

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

Yes — chrome-stealth is associated with the 2026-01-ambertransit 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 chrome-stealth 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 chrome-stealth (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chrome-stealth across your stack and pipelines.

Malicious package

chrome-stealthPyPI

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

MAL-2026-28

Immediate action

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

pip uninstall chrome-stealth

What this malware does

By using the package, the computer is attached to participate in a proxy network and share its IP and bandwidth. This is clearly stated, but the package has no real functionality besides that. Additionally, the stated proxy network seems extremely shady: the domain was just registered, is closely similar to a long-existing service, and offers residential proxy only for cryptocurrencies. The company mentioned in the package information does not have a website, and the proposed way to opt-out does not work.

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

Campaign: 2026-01-ambertransit

Reasons (based on the campaign):

other
modify-system-without-consent

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

a97fed2b45bf12e5c4ba72089cdc2a1aff4ef42cb5eed242565268439946041a

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

Campaign

2026-01-ambertransit

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks chrome-stealth-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