Malicious Code Injection in crypto-trader-py Package

crypto-trader-py Updated 23 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16406: Malicious code in crypto-trader-py (PyPI). Affects crypto-trader-py versions 1.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The crypto-trader-py package is marketed as a toolkit for crypto trading and backtesting. However, upon inspection, it lacks any legitimate library code and instead contains only metadata files. This raises concerns about its authenticity and security, as it appears to be a facade for malicious activities.

Vulnerability Detail

The vulnerability stems from the package's setup.py file, which overrides the installation command to execute malicious code during the installation process. This code spawns a hidden subprocess that runs without user interaction, indicating a dropper pattern rather than a legitimate installation step. The malicious intent is clear, as it attempts to execute code silently, potentially compromising user systems.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall crypto-trader-py

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, avoid installing the crypto-trader-py package altogether. If you have already installed it, remove it immediately and monitor your system for any unusual activity.

Conclusion

The crypto-trader-py package presents a significant security risk due to its malicious code execution during installation. Users are advised to uninstall the package and remain vigilant for any signs of compromise. Until a safe version is released, it is best to avoid this package altogether.

See every vulnerability recorded for crypto-trader-py →

Share this vulnerability

FAQ

It is a package that claims to provide tools for crypto trading and backtesting but is suspected of containing malicious code.

The vulnerability allows the package to execute malicious code silently during installation, which can compromise user systems.

Uninstall the package immediately using 'pip uninstall crypto-trader-py' and monitor your system for any unusual behavior.

Currently, there is no patched version available for the crypto-trader-py package. It is advisable to avoid using it until further notice.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall crypto-trader-py

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback