Which versions of backtradingbot are malicious?

The following PyPI versions of backtradingbot are flagged malicious: 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5. Treat any of these as compromised.

How do I remediate backtradingbot if I installed it?

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

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

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

Malicious package

backtradingbotPyPI

Malicious code in backtradingbot (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191689

Immediate action

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

pip uninstall backtradingbot

What this malware does

Running the installed entry point downloads and executes remote code. During the analysis, the code was switching to websockets, adding a startup script and downloading next stages, which finally looked for browser and crypto wallet data. Currently, they seem not to attempt exfiltration of very sensitive data but rather a presence of different webbrowsers and wallets.

It uses the same remote domain as campaign 2025-07-db-indicator, but significantly different payload.

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

Campaign: 2025-07-backtradingbot

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
peristence-autorun
exfiltration-browser-data
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
crypto-related

Malicious versions

5 flagged

0.1.10.1.20.1.30.1.40.1.5

Indicators of compromise (SHA-256)

e6ba5a032a0d73af329025dde0405bd7f1847f95e6cc19af6a7fb1c448874738

117c24f5b7a0f5e4921e4478231a717ecca01748a5b266d8984e619f06173984

ce3087733438f472d2652f1c18c089932f54dbe353e966b440fe57c30f6a7c75

5d66cb7e375b65f749267ca86c38fc16c318851ec20c7cfdf351f98339720fc5

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

Campaign

2025-07-backtradingbot

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks backtradingbot-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