Which versions of mypypipkg are malicious?

The following PyPI versions of mypypipkg are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate mypypipkg if I installed it?

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

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

Yes — mypypipkg is associated with the 2026-04-old-mypypipkg 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 mypypipkg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mypypipkg (2 malicious versions).

Malicious package

mypypipkgPyPI

Advisory published Apr 27, 2026Updated Apr 27, 2026

mypypipkg is a confirmed malicious PyPI package (MAL-2026-3105) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mypypipkg (PyPI)

MAL-2026-3105

Immediate action

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

pip uninstall mypypipkg

What this malware does

When running as a module, the package starts a VSCode tunnel and exfiltrates the connection link to the hardcoded target. This lets the attacker connect the VSCode instance online and gain remote access to the machine as the user running the code.

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

Campaign: 2026-04-old-mypypipkg

Reasons (based on the campaign):

vscode-tunnel

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

a94a9bbd6a292f754fedd6ae737eaf5259925cf382a610c9d63e9d210a3f3677

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for mypypipkg (2 malicious versions).
If you installed it — respond
mypypipkg 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 mypypipkg 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. mypypipkg on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-old-mypypipkg

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks mypypipkg-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