Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Comodo
Comodo Internet Security 2025 was obliterated by an exploit!
Message
<blockquote data-quote="vitao" data-source="post: 1112832" data-attributes="member: 109212"><p>sorry but youre wrong. the exe has certs but the dll hasnt (atleast is seems so). the dll continues to be ignore by cis, cloud lookup, valkyrie, etc. but even win defender can recognize it. so, no, the test is not wrong and there is nothing to check on logs as cis has no proper log for this dll. just that its not recognized but still its allowed to run on default config.</p><p></p><p>edit.: the confirmation is the file running, ruining personal files and cis doing nothing to prevent it. in this case, with the config changed, cis can prevent the exe to execute but not the dll, so if the exe was with an valid cert vendor (like, lets say, sectigo?), even with this configuration cis would not prevent the exe to run, so...</p><p></p><p>edit.: and the funny part is cruelsister saying that allowing an ransomware to run is a trivial issue...</p></blockquote><p></p>
[QUOTE="vitao, post: 1112832, member: 109212"] sorry but youre wrong. the exe has certs but the dll hasnt (atleast is seems so). the dll continues to be ignore by cis, cloud lookup, valkyrie, etc. but even win defender can recognize it. so, no, the test is not wrong and there is nothing to check on logs as cis has no proper log for this dll. just that its not recognized but still its allowed to run on default config. edit.: the confirmation is the file running, ruining personal files and cis doing nothing to prevent it. in this case, with the config changed, cis can prevent the exe to execute but not the dll, so if the exe was with an valid cert vendor (like, lets say, sectigo?), even with this configuration cis would not prevent the exe to run, so... edit.: and the funny part is cruelsister saying that allowing an ransomware to run is a trivial issue... [/QUOTE]
Insert quotes…
Verification
Post reply
Top
