MAL-2026-20253
Malicious code in besk (crates.io)
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | MAL-2026-20253 divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
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.
Versiones afectadas
0.1.1Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
crates.iobesk |
Sin parche | — | — | — |
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://crates.io/crates/besk/0.1.1Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
