Which versions of my-package-jiecub3 are malicious?

The following PyPI versions of my-package-jiecub3 are flagged malicious: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0. Treat any of these as compromised.

How do I remediate my-package-jiecub3 if I installed it?

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

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

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

Search your lockfiles and build artifacts for my-package-jiecub3 (7 malicious versions).

Malicious package

my-package-jiecub3PyPI

Advisory published Apr 21, 2026Updated Apr 21, 2026

my-package-jiecub3 is a confirmed malicious PyPI package (MAL-2026-2962) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.1.0, 1.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in my-package-jiecub3 (PyPI)

MAL-2026-2962

Immediate action

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

pip uninstall my-package-jiecub3

What this malware does

During installation, the package attempts to create a reverse shell

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

Campaign: 2026-04-my-package-jiecub3

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

7 flagged

1.0.01.1.01.2.01.3.01.4.01.5.01.6.0

Indicators of compromise (SHA-256)

1ec43b076f10c0f300bdde6c106bc020894f238b7b2b72e3a3c146d189bdb3a4

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for my-package-jiecub3 (7 malicious versions).
If you installed it — respond
my-package-jiecub3 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 my-package-jiecub3 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. my-package-jiecub3 on PyPI has been identified as a malicious package (versions 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-my-package-jiecub3

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks my-package-jiecub3-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