besk (crates.io) · Malicious Code
Affects beskSource GCVE Database
Malicious package : remove besk and rotate any secrets on hosts that installed it.
Data as of 19 Nov 2026, 19:04 UTC
Malicious package
Published to crates.io · OSV MAL-2026-20253
What to do
Remove besk from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| crates.iobesk | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1fcb2c7993d79ce401ea84c943e2838258f01ec1ecea1adb7f9fd58b536d4241) The crate ships a user-run binary whose main entry awaits parse::bs() and test::dat(). These routines use dirs::home_dir and WalkDir to enumerate the user's home directory, match wallet/keystore files, compress them with ZipWriter, and transmit them to attacker-controlled destinations: a hardcoded Telegram chat id 7304091279 via the toxtg crate, and the Groq LLM API at api.groq.com/openai/v1 using an in-source gsk_ bearer key. parse.rs and test.rs each embed the live Groq API key and Telegram chat id as const strings. The dependency set additionally stages keystroke capture (rdev 0.5.3, evdev 0.12) and Windows registry access (winreg 0.50 under cfg(windows)), invoked from the same test module. The payload is buried inside ~40-60 KB of nonsense padding functions with randomized identifiers (apply_twice_torvak_78, mix_mirmir_240, Modemir65::Umbfel67, etc.) wrapping the small active block around lines 1230-1540 of parse.rs and test.rs, consistent with deliberate obfuscation to defeat casual review. The package's Russian self-description as a 'cybersecurity learning project' does not match its behavior.