besk (crates.io): malicious Rust crate steals crypto wallet files via Telegram and Groq API
Severity: critical · Patch status: no-fix-needed · Since 2026-11-19
The besk crate (version 0.1.1) on crates.io was identified as malware by Amazon Inspector and reported via OpenSSF/GitHub Advisory Database on 2026-11-19. Its binary enumerates the user's home directory with WalkDir, matches wallet/keystore files, zips them, and exfiltrates them to a hardcoded Telegram chat id (7304091279) via the toxtg crate and to the Groq LLM API using an embedded gsk bearer key. Dependencies stage keystroke capture (rdev, evdev) and Windows registry access. The payload is hidden among ~40-60 KB of obfuscated padding functions with randomized identifiers. The crate's Russian description as a 'cybersecurity learning project' contradicts its behavior. No patched version exists; the crate is malware and has been removed/advisory published. Users who ran besk 0.1.1 should treat wallet keys and credentials as compromised.
What to do
- Remove besk 0.1.1 from all projects and environments immediately
- Rotate any crypto wallet keys, seed phrases, and keystore credentials on machines where the binary was run
- Audit affected hosts for keylogging and registry persistence artifacts; consider full reimage
- Check build/CI logs and lockfiles for accidental inclusion of besk
- Block exfiltration endpoints (Telegram chat id 7304091279, api.groq.com key usage) at network egress
Sources
All live incidents on Threat Watch