![]() |
|
#1
|
||||
|
||||
|
Quote:
|
|
#2
|
|||
|
|||
|
Damn, and I thought I would be safe now, actually surfing with vmware..
but noticed a hook.dll in lots of processes. But the hook in Vmware is nothing dangerous. Last edited by SystemJunkie : March 14th, 2006 at 08:35 AM. |
|
#3
|
||||
|
||||
|
This is similar to the *blue pill* topic that have spawned a bit everywhere in there forum.
This thread is also the continuation of that other one: http://www.wilderssecurity.com/showt...085#post809085 in wich Mrkvonic Posted: Quote:
SO the subject look confusing. This is NOT an idea of rootkit that goes outside the virtual machine and infect the host. This is the idea of a rootkit that infect the host then .... secretly without you being able to see it launch the host as a virtual machine. Basicly the whole Host and security app live inside a virtual machine created by the rootkit. Application inside this machine cannot see the outside ... so they cannot see the rootkit. |
|
#4
|
||||
|
||||
|
Quote:
![]() |
|
#5
|
||||
|
||||
|
Hi,
sorry about that Bubba, this subject has been currant with me at the moment via a talk I gave on this subject, many fingers in pies as the expression goes, and remembered I had that link knocking about to that article which I felt was easy on the reading/understanding - as a start to a discussion. Didnt realise it was five months ago thou time fliesI DO search here, but unfortunetly that one past me by! - sorry ronjor.
__________________
Who controls the past controls the future Who controls the present controls the past vmworld |
|
#6
|
||||
|
||||
|
Quote:
![]() |
|
#7
|
|||
|
|||
|
How can something from within a virtual machine program come out and attack the host operating system? Aren't they separate from each other, the guest and the host OS?
|
|
#8
|
||||
|
||||
|
Quote:
Quote:
what you thought was configured may not be and... ![]() I've had Qs obviously, about whether any av is detecting this. Has this been discussed? Not necessary av. @nadirah (please forgive if this does not read correctly, my english, I hope you get the jist) The idea is to take malicious code and subvirt it from your os. This is achieved through the creation of an additional 'layer,' a VMMonitor, between the os and your hardware. This is when control is lost, bypassed through the VMMonitor. Then the new normality launches another os where the malicious code is executed! This malicious progam is then in direct contact with the hardware and undetectable by the users os ![]() |
|
#9
|
||||
|
||||
|
Not looking good:
http://www.bluetack.co.uk/forums/ind...howtopic=14935
__________________
Don't confuse me with someone who actually knows what they are talking about. Linux Registered user 469135 Please, support Medecins Sans Frontieres |
|
#10
|
||||
|
||||
|
Quote:
Theres alot of infections that can circumnavigate detectors, this one hides in alternative data streams which are further hidden via a rootkit. It is now detectable, although its a constant battle with well know rootkit scanners such as F-Secures blacklight. That is why when time permits I'm playing with the system virginity verifier (svv) source. The different versions produced with this source will be harder to beat. Anyway there are a few exploits now which are very nasty Last edited by Meriadoc : August 11th, 2006 at 03:41 PM. |
|
#11
|
|||
|
|||
|
I don't think the biggest threat is the attacks on already installed VM software, such as VMware. I think the biggest threat is rootkit software using similar technology to VMware that installs a rootkit between the hardware and os.
I think this is the idea behind the 'blue pill' software that there is soo much hype about. |
|
#12
|
||||
|
||||
|
alch :
Quote:
Quote:
Quote:
Quote:
|
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|