Open MalwareTips from your Home Screen or desktop. Follow discussions, find answers and pick up where you left off.
If you cannot find an install option, update your browser or use its bookmark option to keep MalwareTips close.
After installation, open the app and sign in. Enable push notifications in Preferences if you want alerts. On iPhone and iPad, push requires a Home Screen web app and iOS or iPadOS 16.4 or later.
Sign in to manage notificationsInstallation is optional. Your notification settings stay under your control.
I read the description of that protection on Comodo help, and according to what I understood, I really think it should have prevented file modification, when you used a third-party tool. Best to bring it up on the Comodo forum and see what they have to say.I guess there is a big bug which Comodo missed it.shmu can you pls try this? add smth to that protected files/folders and try to remove the file with a third-party tool or by yourself!
Found the Same problem with Eset hips! because they don't care about the hash(they only consider the PATH or name)! but Rehips care about the hash!this is the strong point with RehipsI replaced a valid program file with a cracked one
just added C:\Users\Sunshine-boy\AppData\Local\Yandex\YandexBrowser\Application \browser.exe to Protected Files>important files and folders.
Then removed/renamed the file but hips didn't alert or block my actions on this file?!whats wrong? shouldn't protect the file from changes?
Probably because they are the ones who have a chance of bypassing HIPS without paranoid settingsDo you really think the people at kernelmode.info, who are GODs who laugh about us, use HIPS software with "paranoid settings"? I sincerely doubt that.
As you can see comodo log the action(Comodo won't tell me what was that ? remove or rename? no information) for this file but the problem is it didn't block the action! comodo log it as blocked action but the file is in Recycle Bin
It probably bypasses API hooks for file removal with a system call to NtDeleteFile, or it uses a kernel-mode device driver to remove files without triggering NtDeleteFile hook on SSDT/FltRegisterFilter callback.Even with hips in paranoid mode and costume settings for pc hunter( block access for protected files/folders)! I can force remove protected files with it! Idk what is it?
I changed the name and Comodo didn't react I also removed the file but again comodo dint care! hips in paranoid and settings are set to proactive mode.name then deleted the folder or just deleted the folder
Hacker xd I guess you are right because the tool creates a driver!!but I have A block rule for MY file! hips should avoid it! whats the solution for such things opcode? what if there is a malware that can do such thing?and how Hips can handle it?device driver
Malware can do these things and it could have done them for years. If we take a step back to the times around 2006 - 2012 there was some really deadly threats from those times surrounding rootkit infections which could do complex and sophisticated things, applying techniques to surpass behavioural prevention. However, without a bypass for PatchGuard (Driver Signature Enforcement feature specifically), you must have a signed device driver on 64-bit systems. Due to this, and due to many people moving to 64-bit over the many years since such a feature was introduced back on Windows Vista, the malware in the wild has significantly changed.
I've seen cases where an unsigned driver has been attempted to be loaded, but has been blocked from doing so followed by an on-screen prompt to the user saying that the activity was prevented due to the certificate issue. However, I've only seen it happen a few times myself whilst on Windows 7 using genuine tools to automatically create and start services for device drivers, therefore I am not entirely sure. I believe it was some sort of "information" alert with only OK as the option, as opposed to a security-warning "stay alert" sort of warning.Thanks for such a detailed explanation. Does Windows report an attempt to do this with any sort of pop up notification of the block like an error box or anything? Never seen one before.
It is certainly much more difficult but as far as I am aware there is a decent work-around to PatchGuard for Driver Signature Enforcement which works on Windows 10 - it evolves around exploitation of the genuine VirtualBox device driver.So it's harder to get rootkits on a 64 bit system, partly because the driver has to be signed. I can understand that. Should I hope still that this hasn't made security devs feel at ease about monitoring for attempts? If someone finds a way to use a valid signature somehow (maybe unlikely) then maybe this could be a problem still. Also, sounds like 32 bit OS uses are at risk. Should they be concerned?
Members and guests who viewed this thread in the last 5 minutes
We use essential cookies to make this site work, and optional cookies to enhance your experience.