Which versions of proxy-check-ii are malicious?

The following PyPI versions of proxy-check-ii are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate proxy-check-ii if I installed it?

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

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

Yes — proxy-check-ii is associated with the 2026-07-proxy-check-i 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 proxy-check-ii 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 proxy-check-ii (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 proxy-check-ii across your stack and pipelines.

Malicious package

proxy-check-iiPyPI

Malicious code in proxy-check-ii (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-10610

Immediate action

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

pip uninstall proxy-check-ii

What this malware does

The embedded binary starts a relayed SSH-like server using a hardcoded authorized_key. Thanks to using a relay network, the attacked does not need to directly expose ports from the machine.

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

Campaign: 2026-07-proxy-check-i

Reasons (based on the campaign):

backdoor
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

8a222abeb680e48d3cffbdeb7f0d6cba713b023d825b2c42c7a849b36b2fe0a5

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 proxy-check-ii (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 proxy-check-ii across your stack and pipelines.
If you installed it — respond
proxy-check-ii 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 proxy-check-ii 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 proxy-check-ii 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. proxy-check-ii 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-07-proxy-check-i

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks proxy-check-ii-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