Which versions of chunqiuwestj-pkg-westj137 are malicious?

The following PyPI versions of chunqiuwestj-pkg-westj137 are flagged malicious: 0.3.0. Treat any of these as compromised.

How do I remediate chunqiuwestj-pkg-westj137 if I installed it?

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

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

Yes — chunqiuwestj-pkg-westj137 is associated with the GENERIC-standard-pypi-install-pentest 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 chunqiuwestj-pkg-westj137 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 chunqiuwestj-pkg-westj137 (version 0.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chunqiuwestj-pkg-westj137 across your stack and pipelines.

Malicious package

chunqiuwestj-pkg-westj137PyPI

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

MAL-2024-12235

Immediate action

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

pip uninstall chunqiuwestj-pkg-westj137

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.3.0

Indicators of compromise (SHA-256)

0d7a8fc6ba1ad64f36c6e62ec17a1a85007b089841d7e8581b2175bfc7eac1ed

03ad250cd789424d92dd1351d15a218d3950be367950c4fc129cf866423a7b8e

fe3c7feab55eb5454322bf516a4656107b5f9020b163a3caa738fd05d342f60e

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 chunqiuwestj-pkg-westj137 (version 0.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chunqiuwestj-pkg-westj137 across your stack and pipelines.
If you installed it — respond
chunqiuwestj-pkg-westj137 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 chunqiuwestj-pkg-westj137 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 chunqiuwestj-pkg-westj137 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. chunqiuwestj-pkg-westj137 on PyPI has been identified as a malicious package (version 0.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks chunqiuwestj-pkg-westj137-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