Which versions of lbank-connector-pythons are malicious?

The following PyPI versions of lbank-connector-pythons are flagged malicious: 2.0, 2.1, 2.2, 2.3. Treat any of these as compromised.

How do I remediate lbank-connector-pythons if I installed it?

lbank-connector-pythons 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 lbank-connector-pythons — how do I know if it already compromised me?

If lbank-connector-pythons 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 lbank-connector-pythons part of a known attack campaign?

Yes — lbank-connector-pythons is associated with the RLMA-2025-05615, GENERIC-standard-pypi-install-pentest, RLUA-2026-00466 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 lbank-connector-pythons 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 lbank-connector-pythons (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lbank-connector-pythons across your stack and pipelines.

Malicious package

lbank-connector-pythonsPyPI

Malicious code in lbank-connector-pythons (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191644

Immediate action

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

pip uninstall lbank-connector-pythons

What this malware does

This is a copy of a legit package with added basic exfiltration in the setup.py

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

4 flagged

2.02.12.22.3

Indicators of compromise (SHA-256)

be860829dcedc2bf0981c76c1ea75b885957e544a964d28cf69695e3ee2ac9ed

a8ac8a9f87c9d93340528329867082207c0437ad9fe6d31408cf7754b5705ad9

8e2d03134723d75ab2f0b36c6acad54fa5d16b4ba0f04bf2705e188fd19626b9

50f436f344f514099ea2389611705259c9094e8f2f6a0faf819c43aa71987599

4582809a7633a72953e4b02ed264609834dec8a8df6efab777fb50fc9d0db89e

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

Campaign

RLMA-2025-05615GENERIC-standard-pypi-install-pentestRLUA-2026-00466

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks lbank-connector-pythons-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