Which versions of proxy-rubikis are malicious?

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

How do I remediate proxy-rubikis if I installed it?

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

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

Yes — proxy-rubikis is associated with the 2026-10-proxyrubika 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-rubikis across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for proxy-rubikis (version 0.1.0).

Malicious package

proxy-rubikisPyPI

Advisory published Oct 15, 2026Updated Oct 15, 2026

proxy-rubikis is a confirmed malicious PyPI package (MAL-2026-17887) 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 proxy-rubikis (PyPI)

MAL-2026-17887

Immediate action

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

pip uninstall proxy-rubikis

What this malware does

The package contains code for automated files exfiltration.

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

Campaign: 2026-10-proxyrubika

Reasons (based on the campaign):

files-exfiltration
target:android

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

0326ad29540efd267d15181087b384b25da962e7bcd6ac40c39641699e212e50

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for proxy-rubikis (version 0.1.0).
If you installed it — respond
proxy-rubikis 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-rubikis 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. proxy-rubikis 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-10-proxyrubika

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks proxy-rubikis-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