Dossier

Shivam

aka SilentHex (GitHub)

Engineer — Code Contributor during Vulnerability Preservation

Photographs

Charges

• Count 4: Computer Fraud
• Count 5: Conspiracy

What this defendant knew

As an engineer with commit access, Shivam possessed technical knowledge of: (1) the protocol's smart contract architecture, (2) any vulnerability assessments conducted, (3) the decision not to patch the PT-LBTC oracle flaw after the May 2024 Blast exploit.

Intent indicators

• Continued code contributions (if any post-May 2024) without patching known vulnerability
• Possessed zerolend.xyz email — indicating insider status, not external contractor
• GitHub activity (if any) during concealment period suggests continued participation in operational deception

Public identity traces

• GitHub: SilentHex (shivam@zerolend.xyz)

Prosecution's theory

If Shivam was an engineer with knowledge of the vulnerability who failed to advocate for a patch, his technical expertise creates an elevated duty. The prosecution's theory: engineers who continue working on a vulnerable protocol without pushing for fixes are aiding the concealment. If his GitHub commits ceased after exploit discovery (suggesting he knew and left), he remains an accessory. If he continued committing code post-exploit, he escalated to co-conspirator.

Incriminating exhibits

• Exhibit D-16: GitHub commit history

  Timeline of code contributions relative to exploit dates

Proofs & Evidence Collection

The following evidentiary items are preserved in this repository. Each item is timestamped, verifiable on public block explorers or web archives, and subpoena-ready for law enforcement. File paths reference the local evidence archive; URLs link to live public sources.