AI enthusiast mods BIOS with Claude Code, defeats RSA-2048 signature checks

An AI enthusiast used **Claude Code** to reverse-engineer and modify a laptop BIOS, bypassing **RSA-2048** signature verification and exposing **55** previously locked settings. Tom’s Hardware covered the work; a related Hacker News thread (Claude/Codex/Fable) listed four points and no comments at the time of the summary.

The technical core is the chain of trust around firmware: vendors sign BIOS images so loaders reject unsigned or altered binaries. RSA-2048 is a common choice for that check. Defeating it means the modified image still presents as valid to the signature gate—or the check is patched out—so the firmware accepts changes that would normally be blocked. Unlocking dozens of hidden options points at OEM-restricted knobs (power, thermals, devices, debug paths) that the stock UI never surfaces.

For engineers and builders, this is a live case of an agent-assisted workflow on low-level code: reading firmware structure, locating signature validation, and producing a working mod without a traditional reverse-engineering shop. It compresses the loop from “opaque binary + public docs” to “interactive debugging with an AI coding tool,” which raises the bar for anyone who assumes RSA-signed firmware is out of reach for non-specialists.

In the market, laptop makers use signed BIOS and locked settings to control warranty, compliance, and support surface. Tools like Claude Code (and peer agents discussed on HN under Claude/Codex/Fable) lower the skill floor for firmware tampering relative to hand-written RE. That does not make every machine trivially unlockable, but it does change how vendors should model threat and capability: hobbyists can now iterate on signature bypasses with less specialist tooling.

Practical takeaway: treat “signed BIOS” as a policy and UX boundary, not a guarantee against determined local attackers with AI assistance. Watch whether OEMs respond with stronger secure-boot chains, hardware-rooted keys, or more aggressive anti-tamper—and whether agent-driven firmware work spreads beyond one enthusiast’s 55 unlocked settings into broader, repeatable unlock kits.