Fired hacker twins forget to end Teams recording, capture own crimes
Briefly

Fired hacker twins forget to end Teams recording, capture own crimes
"SOHAIB: "Still connected? Still on the VPN?" SOHAIB: "Delete all their databases?" MUNEEB: "Eh, they can recover them...backups, I'm pretty sure." SOHAIB: "Daily backups?" MUNEEB: "Yup." SOHAIB: "What's the plan [then]? We gonna take care of severance or are we gonna do something about..." "Should we retort to whatever they send us by saying we need $25,000 each? Hm?""
"MUNEEB: "I'm going to wipe my computer clean." SOHAIB: "I can't access the system but I still have the email address for their customers for eCase and FOIAXpress." MUNEEB and SOHAIB discuss being compensated by Company-1. MUNEEB: "I'm not gonna threaten them shit, that's like could be shown as some sort of . . ." SOHAIB: "It depends on how you write it. Just say, 'according to our previous agreement, this is the tally of the amount that I've been [paid], if you pay it up front, then I have no reason to communicate with customers.'""
"MUNEEB: "People are logged out for the day, this is the perfect time." SOHAIB: "How do you still have access? When did you connect to their VPN?" MUNEEB: "10 minutes before their stupid meeting." SOHAIB: "You might still have access to it until the end of the day. Until at least 6 hours." MUNEEB: "Don't worry about it man. Don't worry about it.""
Two people coordinate cybercriminal activity while connected to a VPN. They discuss deleting databases and whether daily backups allow recovery. They talk about compensation from a company and consider how to phrase demands to avoid communicating with customers. One person plans to wipe a computer clean. They note limited access to a system but retain email addresses for customers tied to specific services. They discuss not threatening victims and not snitching, while timing actions for when people are logged out. They question how one person still has access and when the VPN connection occurred, estimating how long access may last.
Read at Ars Technica
Unable to calculate read time
[
|
]