NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

beskcrates.io

Advisory published Updated

besk is a confirmed malicious crates.io package (MAL-2026-20253) that steals credentials and exfiltrates sensitive data (malicious version 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in besk (crates.io)

MAL-2026-20253
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
remove besk

What this malware does

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.

Malicious versions

1 flagged
0.1.1

Indicators of compromise (SHA-256)

1fcb2c7993d79ce401ea84c943e2838258f01ec1ecea1adb7f9fd58b536d4241

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for besk (version 0.1.1).

  2. If you installed it — respond

    besk 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.

  3. Did it already run?

    If besk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. besk on crates.io has been identified as a malicious package (version 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022890

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks besk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

besk (crates.io) malicious package — MAL-2026-20253 | O3 Security