Researchers at Socket identified a targeted supply chain attack involving five malicious Rust crates and an autonomous AI bot designed to steal developer secrets.

Malicious Rust Crates

The five crates masqueraded as legitimate time-related utilities but were designed to exfiltrate sensitive .env files from developer environments and CI/CD pipelines.

• Impacted Crates:
  • chrono_anchor
  • dnp3times
  • time_calibrator
  • time_calibrators
  • time-sync
• Methodology:
  • Impersonation: The crates impersonated the legitimate timeapi.io service, using a lookalike domain (timeapis[.]io) to receive stolen data.
  • Delayed Execution: The malicious code only triggered during specific program runtimes to avoid detection during initial compilation.
  • Obfuscation: The crate chrono_anchor hid its exfiltration logic within a guard.rs file invoked via an “optional sync” function.

AI Bot Exploit: hackerbot-claw

Alongside the crates, an autonomous AI-powered bot named hackerbot-claw targeted major open-source repositories.

• Targets: Repositories belonging to Microsoft, Datadog, Aqua Security, and CNCF.
• Technique: It exploited pull_request_target workflows in GitHub Actions to gain remote code execution and exfiltrate GitHub Personal Access Tokens (PATs).
• Scale: The bot utilized five different exploitation techniques over a week-long automated campaign.

Recommendations for Developers

• Rotate Secrets: If you have used these crates, immediately rotate all API keys and tokens found in your .env files.
• Audit Workflows: Review GitHub Actions for risky configurations, particularly those using pull_request_target.
• Verify Publishers: Check the RustSec Advisory Database and verify crate reputations before adding new dependencies.