App Review Comodo Internet Security vs targeted ransomware attack.

It is advised to take all reviews with a grain of salt. In extreme cases some reviews use dramatization for entertainment purposes.
Content created by
me
The Advanced Threat Protection tests included in my previous post were slightly outdated.
So, I inspected the attack vectors included in newer tests (do not include CIS/CCS/Xcitium).


The newer tests include some of the methods that might bypass CIS (such as DLL hijacking). However, the required methods are applied at the later infection stages, when the attack is already contained. For example (the red part of the attack can be auto-contained):

Email with attachment ---> EXE or script file in the archive ----> EXE or script file unpacked/executed ----> ... ----> DLL hijacking

It is rather clear that the used attack vectors are prepared to bypass NextGen solutions and do not bother to bypass Comodo.
 
AV-Comparatives Advanced Threat Protection tests.


One of the scenarios used in the tests can bypass CIS (as I mentioned in my previous posts).
Advanced Threat Protection Test 2022 - Enterprise

15. This threat is introduced via Removable Media. A malicious office document injects into another user-space process and opens a C2 channel to a commercial C2 framework via https.

Documents on infected removable media do not have Mark of the Web, so macros are not blocked by default in MS Office. The attacker can use VBA code that applies PE injection. The code is well known and effective against CIS (I tested it some time ago). In this case, the VBA macro does not invoke PowerShell, Windows Script Host, or anything that Comodo Script Analysis could block. Other security solutions can use AMSI-based detections to prevent the attack.
 
Last edited:
Some notes about the risk of using trojanized NPM packages at home.

Trojanized NPM package ---> malicious Node addon loaded ---> malware executed filelessly in the memory of the Node executable

In theory, such addons might be detected by Comodo via signatures or Viruscope. However, I would not place much hope in these protection layers for protection against new threats.

On the other side, such attacks require installing the Node.js runtime, which is probably rare at home (except for software developers or tech hobbyists).
Anyway, there were some in-the-wild examples of using portable/archived versions of Node.js environment. I must research those examples to get some insight.

Update.
The known attacks with portable/archived Node.js runtime were mainly initiated via PowerShell, so they could be auto-contained by CIS.
The attackers would have to use another Trusted script interpreter (unrestricted by Comodo Script Analysis) to bypass CIS. This is improbable, except for a highly targeted attack.
 
Last edited: