CPU remotely accessed, Erased All my Videos! dahboo77

[Serpo]

he dosnt sound very happy


http://www.youtube.com/watch?v=aXztTHYKMAg

[Shami-Amourae]

:p
@3:41

https://www.youtube.com/watch?v=emmbx_o-OKg

[StreetsOfGold]

:p
@3:41

Why would a guy with only 258 subscribers think he is a target? At least with 100,000+ This dahboo77 guy has a case

[Shami-Amourae]

Why would a guy with only 258 subscribers think he is a target? At least with 100,000+ This dahboo77 guy has a case

He's a troll.

[Glass]

do none of these people off line their material? Seems odd to me.

[Ares]

Ask him to call the NSA, I'm sure they have a backup of all his data. :D

[mick silver]

hit the nail on the head ares

[PatColo]

besides msft and aapl having nsa backdoor welcome mats integrated in their closed-source OS's; I've always suspected the hardware makers also had this too, lest a user run an open source OS like linux...


NSA BIOS Backdoor a.k.a. God Mode Malware Part 1: DEITYBOUNCE (http://grizzom.blogspot.com/2014/08/nsa-bios-backdoor-aka-god-mode-malware.html)

http://grahamcluley.com/wp-content/uploads/2013/12/bios-thumb.jpeg (http://grahamcluley.com/wp-content/uploads/2013/12/bios-thumb.jpeg)

The DEITYBOUNCE core functions above imply that there are possibly three kinds of malware components required for DEITYBOUNCE to work as follows:


A persistent “infected” PCI expansion ROM. This module contains a routine to configure DEITYBOUNCE’s frequency of execution. The routine possibly stores the configuration in the RAID controller NVRAM. This module also contains the tainted interrupt 13h (Int 13h) handler that can call other routines via SMI to patch the kernel of the currently loading OS.

SMI handler(s) code implanted in the PowerEdge motherboard BIOS to serve the software (SW) SMI calls from the “infected” RAID controller PCI expansion ROM.

An OS-specific malware payload running in Windows 2000, Windows Server 2003, or Windows XP.


At this point we already know the DEITYBOUNCE malware components. This doesn’t imply that we would be able to know the exact architecture of the malware, because there are several possible pathways through which to implement the components. However, I present the most probable architecture here. This is an educated guess. There could be inaccuracies because I don’t have a sample DEITYBOUNCE binary to back up my assertions. But I think the guesses should be close enough, given the nature of x86/x64 firmware architecture. If you could provide a binary sample with suspected DEITYBOUNCE in it, I’m open to analyze it, though :-).

***Read full article here*** (http://resources.infosecinstitute.com/nsa-bios-backdoor-god-mode-malware-deitybounce/)

[Hatha Sunahara]

No need to go to the NSA for your videos. When you erase something from your hard disk, it's still there, but it exists in a part of the drive called 'free space'. All you need is a recovery program, and you can restore it. Unless of course it was shredded and written over with zeros or random bytes. But that would take a long long time, and not very likely.


Hatha

[PatColo]

^ CCleaner for windoze and BleachBit for Ubuntu Linux both have the option to overwrite deleted files. :)

[Horn]

Probably a bitcoin and dell user.

[Silver Rocket Bitches!]

I've had success with Recuva in the past. If the file was recently deleted and there hasn't been enough time for other files to write over those sectors, that is.

http://www.piriform.com/recuva