Which versions of bancor-simulation are malicious?

The following PyPI versions of bancor-simulation are flagged malicious: 20.0. Treat any of these as compromised.

How do I remediate bancor-simulation if I installed it?

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

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

Yes — bancor-simulation is associated with the RLMA-2025-00440, 2024-12- sajansubedi, RLUA-2026-00135 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 bancor-simulation 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 bancor-simulation (version 20.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bancor-simulation across your stack and pipelines.

Malicious package

bancor-simulationPyPI

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

MAL-2025-902

Immediate action

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

pip uninstall bancor-simulation

What this malware does

The package looks like a beginning for a further work. In fact, the uploader has shortly published a few similar packages appearing to be e.g. an integration for a known application, but containing only a "telemetry" module exfiltrating basic info about the user. This package has no other purpose than collecting data about users. In addition, it appears to be largely generated by an LLM.

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: 2024-12- sajansubedi

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.
dependency-confusion

Malicious versions

1 flagged

20.0

Indicators of compromise (SHA-256)

8e7aa36a37f7cb90aa58cb6535e017d69b26b83c6ea0ea270a4a08cbc504dc51

46daf0e234984372045674d08d940536b2260484f6f3f0e3f51c84c126dff8f5

8e9ecf6b613a42c070932a842fc4ebe81508d28adbb0aecee9aebe4e530acc0a

0bebb0c7ec82b3d799d7b623e90def23e27d6c97b40dce38b1e8ed5767031f03

416a1d6648fbd222f6c46644d0dd8a0a02f266d85d5810ad3a56219f900305ab

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

Campaign

RLMA-2025-004402024-12- sajansubediRLUA-2026-00135

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks bancor-simulation-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