Ok kids, what did we learn here? Use obfuscation in your kill switches, and place it by leaving vulnerabilities that are “accidental”.
Secondary lesson: don’t web surf on corporate laptops
this post was submitted on 10 Mar 2025
44 points (97.8% liked)
Tech
2409 readers
77 users here now
A community for high quality news and discussion around technological advancements and changes
Things that fit:
- New tech releases
- Major tech changes
- Major milestones for tech
- Major tech news such as data breaches, discontinuation
Things that don't fit
- Minor app updates
- Government legislation
- Company news
- Opinion pieces
founded 2 years ago
MODERATORS
Not a programmer but he was absolutely terrible at hiding his tracks.
Not using any time delay in its triggering so as soon as he was laid off his gifts went off.
Using a system only he has access too.
Using the work computer to search for it and obviously develop it on a dual boot.
I mean seriously... He made no attempt to avoid being caught.
I know the town he was convicted in, it’s not quite a bedroom community for Houston. A bit too far out. They have a problem with the police allowing firearms used in the city limits.
He was convicted by jury there
Or, you know, don't do it in the first place.
I wouldn’t. But there are so many employers, some actually doing evil things, and in some countries sabotaging things while your department is mass fired is all the rage.
So, if one is going to do it, do it well
Absolutely wild that he put his name in that check for his AD status. Not that there's a way around being 100% untraceable, but at least a little bit of obfuscation would have been better.
Regardless of what he named his script it's still checking his account. No amount of obfuscation would make this less stupidly obvious
atta boy!
Good for him!
In my company we call those features and bug fixes