Which versions of expkg-am are malicious?

The following PyPI versions of expkg-am are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate expkg-am if I installed it?

Remove expkg-am from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed expkg-am — how do I know if it already compromised me?

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

Yes — expkg-am is associated with the GENERIC-simple-tests 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 expkg-am 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 expkg-am (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging expkg-am across your stack and pipelines.

Malicious package

expkg-amPyPI

Malicious code in expkg-am (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12268

Immediate action

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

pip uninstall expkg-am

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

edc1b06dcbef9c6df87dce72638feee882677d421e0332fcfa8fe691cb317c27

36b7980049911172764372f2e4d93b74e1ff019b9c6f9860be544e91f7f79a28

cdb2503d186c01cd0b74619c6cb565c99937ec817ccbc69311673c9b4eb79ec3

2448ebed3409cb5b2011e94a4df6b73dddf851463871c41469383bd2a7b41a59

2d65d3a0e336c6bb76ea42bb8621845d38bef2435f7c438c3ab9cffc0f6a7b79

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for expkg-am (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging expkg-am across your stack and pipelines.
If you installed it — respond
Remove expkg-am from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If expkg-am 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 expkg-am 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. expkg-am on PyPI has been identified as a malicious package (version 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-simple-tests

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks expkg-am-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring