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: 1111333" data-attributes="member: 109212"><p>I see. So the file would probably download something that was really dangerous, but the remote server was down, and that's why CIS doesn't detect anything dangerous. Is that it?</p><p></p><p>If that's the case, then something doesn't make sense for two reasons:</p><p></p><p>1) If you look at VirusTotal now, you'll see that the number of engines detecting only this executable as a Trojan is increasing, and if the supposed remote server is down, it means that the engines are detecting the executable as dangerous and not what it would download from the remote server. Therefore, CIS failed to recognize this file as dangerous.</p><p></p><p>2) If the executable isn't dangerous, but rather some file that it would supposedly download, then CIS also failed to identify an attempt to connect to an unknown remote server. Even if the server is down, the executable hasn't been changed, so it would be trying to connect to this server, regardless of whether it's offline or not. At most, it would try to connect or check if the server is online and if it is not, it would not try to establish a connection. However, some network interaction would still be necessary for this verification and this interaction should be intercepted by the CIS and it should warn about it, which does not happen.</p><p></p><p>Considering what you explained, one could conclude that this could perhaps be classified as just an undesirable program and not as malware, but the identifications of more than 40 engines make it clear that it is a Trojan.</p><p></p><p>Considering everything you mentioned, a more detailed analysis that was being carried out until a few minutes ago and the results obtained by other engines, I will keep the video online because until proven otherwise, it is malware and Comodo Internet Security was not able to identify anything about it or its actions (or attempted actions), while many others identify it immediately. But I will add an update to the video description explaining this situation.</p><p></p><p>Or do you think I am wrong in this decision?</p></blockquote><p></p>
[QUOTE="vitao, post: 1111333, member: 109212"] I see. So the file would probably download something that was really dangerous, but the remote server was down, and that's why CIS doesn't detect anything dangerous. Is that it? If that's the case, then something doesn't make sense for two reasons: 1) If you look at VirusTotal now, you'll see that the number of engines detecting only this executable as a Trojan is increasing, and if the supposed remote server is down, it means that the engines are detecting the executable as dangerous and not what it would download from the remote server. Therefore, CIS failed to recognize this file as dangerous. 2) If the executable isn't dangerous, but rather some file that it would supposedly download, then CIS also failed to identify an attempt to connect to an unknown remote server. Even if the server is down, the executable hasn't been changed, so it would be trying to connect to this server, regardless of whether it's offline or not. At most, it would try to connect or check if the server is online and if it is not, it would not try to establish a connection. However, some network interaction would still be necessary for this verification and this interaction should be intercepted by the CIS and it should warn about it, which does not happen. Considering what you explained, one could conclude that this could perhaps be classified as just an undesirable program and not as malware, but the identifications of more than 40 engines make it clear that it is a Trojan. Considering everything you mentioned, a more detailed analysis that was being carried out until a few minutes ago and the results obtained by other engines, I will keep the video online because until proven otherwise, it is malware and Comodo Internet Security was not able to identify anything about it or its actions (or attempted actions), while many others identify it immediately. But I will add an update to the video description explaining this situation. Or do you think I am wrong in this decision? [/QUOTE]
Insert quotes…
Verification
Post reply
Top