Cloud engineer gets 2 years for wiping ex-employer's code repos
A U.S. cloud engineer has been sentenced to prison for remotely wiping his former bank employer’s GitHub repositories and inserting “taunts” in the code after being fired for plugging in a USB drive containing pornography to a work computer. Commenters focus on how easily such damage can be mitigated with proper access revocation, backups, branch protections, and HR–IT coordination, noting that the bank left his credentials active after termination. The case also prompts debate over corporate policies on USB devices and pornography, differences in employment and legal liability between the U.S. and Europe, and the role of federal agencies like the Secret Service in protecting financial infrastructure.
Repo deletion, GitHub behavior, and backups
- Several comments note that deleting a GitHub repo is reversible for some time, and even force-pushing empty refs may be recoverable via GitHub support.
- Others point out that many enterprises use custom or different systems, and may not have robust or tested restore procedures.
- Some assume at least one engineer would have a recent local clone, but others note that “cloud dev environments” and container-only workflows reduce that safety net.
- Branch protection is called out as easy to enable but also easy to disable; GitHub’s garbage collection behavior may keep commits around for a while, but this is treated as uncertain.
USB drive, pornography, and corporate policies
- Large subthread debates whether connecting a USB drive with pornography is a reasonable firing offense.
- Some report zero-tolerance porn policies at regulated firms and say this is common; others find it odd to specify “porn” instead of just “unauthorized USB.”
- People highlight that many organizations formally discourage or block USB use altogether due to security risks, though in practice exceptions and “sneakernet” remain common.
- There’s also a side discussion about why anyone would use a work device for porn when phones and personal laptops exist.
Access termination and internal controls
- Many argue the employer’s IT/HR processes failed by leaving the account active after termination; auto-deprovisioning via HR systems is mentioned as a best practice.
- Counterpoint: this should not reduce the ex-employee’s culpability; recognizing both the crime and the control failure is not “victim blaming.”
- Stories are shared of access not being revoked, laid-off staff retaining systems, and managers mishandling terminations, sometimes causing data loss.
Legal consequences, region differences, and enforcement
- Discussion on whether similar sabotage would lead to jail time in the EU: some say you’d mainly pay damages; others note prison is possible for large, intentional harm.
- Debate over whether stronger worker protections in some regions increase employer risk and thus lower pay; views differ.
- Users clarify that U.S. Secret Service has a financial systems protection role, explaining its involvement alongside or instead of the FBI.
Miscellaneous reactions
- Some compare this to sabotaging physical machinery: same principle, different medium.
- The “grok” taunts in the code are widely mocked as a trivial, almost comical detail in the case.