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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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?

Search your lockfiles and build artifacts for chrome-stealth (version 0.1.0).

Malicious package

chrome-stealthPyPI

Advisory published Jan 3, 2026Updated Jan 3, 2026

chrome-stealth is a confirmed malicious PyPI package (MAL-2026-28) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chrome-stealth (PyPI)

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
Search your lockfiles and build artifacts for chrome-stealth (version 0.1.0).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Explore

All malware advisories How O3 detects malware Vulnerability database