What does the aphorism-lib malware do?

Importing the module starts a telegram bot that connects to a chat and executes provided commands Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-07-talbat Reasons (based on the campaign): - The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine. - The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Which versions of aphorism-lib are malicious?

The following PyPI versions of aphorism-lib are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate aphorism-lib if I installed it?

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

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

Yes — aphorism-lib is associated with the 2025-07-talbat 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 aphorism-lib 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 aphorism-lib (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aphorism-lib across your stack and pipelines.

Malicious package

aphorism-libPyPI

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

MAL-2025-191683

Immediate action

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

pip uninstall aphorism-lib

What this malware does

Importing the module starts a telegram bot that connects to a chat and executes provided commands

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

Campaign: 2025-07-talbat

Reasons (based on the campaign):

The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d1071160fbae021469c72523d1eaef691be59c18ce50308503fa46210e8f5a25

95f15b2b497431703ff51667a4055e8172f9202aeeea0f725b0b0550812f3299

187b6bc80da49b9607cedf879d1a1870b5d487d8077eca1c8357d9abd30a3abf

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

Campaign

2025-07-talbat

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks aphorism-lib-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