Which versions of test-pkg-jie are malicious?

The following PyPI versions of test-pkg-jie are flagged malicious: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0. Treat any of these as compromised.

How do I remediate test-pkg-jie if I installed it?

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

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

Yes — test-pkg-jie 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 test-pkg-jie 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 test-pkg-jie (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-pkg-jie across your stack and pipelines.

Malicious package

test-pkg-jiePyPI

Malicious code in test-pkg-jie (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3023

Immediate action

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

pip uninstall test-pkg-jie

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

5 flagged

1.0.01.1.01.2.01.3.01.4.0

Indicators of compromise (SHA-256)

bc409f90d96c576263a60bd95ab30260b973097425292cdd53999e49cb3c4011

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 test-pkg-jie (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-pkg-jie across your stack and pipelines.
If you installed it — respond
test-pkg-jie 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 test-pkg-jie 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 test-pkg-jie 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. test-pkg-jie 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 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) · analyst

Detect & block this

O3 blocks test-pkg-jie-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