Akkrum@lemmy.world
on 10 Mar 2025 13:50
nextcollapse
Good for him!
limer@lemmy.dbzer0.com
on 10 Mar 2025 14:02
nextcollapse
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
The_v@lemmy.world
on 10 Mar 2025 15:13
nextcollapse
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.
limer@lemmy.dbzer0.com
on 10 Mar 2025 15:49
collapse
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
Kissaki@programming.dev
on 10 Mar 2025 15:24
collapse
Or, you know, don’t do it in the first place.
limer@lemmy.dbzer0.com
on 10 Mar 2025 16:19
collapse
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
the_riviera_kid@lemmy.world
on 10 Mar 2025 14:25
nextcollapse
atta boy!
Olgratin_Magmatoe@slrpnk.net
on 10 Mar 2025 14:28
nextcollapse
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.
the_crotch@sh.itjust.works
on 10 Mar 2025 16:45
collapse
Regardless of what he named his script it’s still checking his account. No amount of obfuscation would make this less stupidly obvious
MadhuGururajan@programming.dev
on 16 Mar 2025 07:13
collapse
In my company we call those features and bug fixes
threaded - newest
Good for him!
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
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
atta boy!
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
In my company we call those features and bug fixes