- Jun 21, 2011
- 376
AVG has a better UI I think ... I always liked it better been using it from 2008 and on but quit using in 2017 and now i am back again.... kindda
Any views or opinions expressed are that of the member giving the information and may be subjective.
This software may behave differently on your device.
We encourage you to compare these opinions with others and take informed decisions on what security products to use.
Before buying a product you should consider factors such as price, ease of use, compatibility, and support. Installing a free trial version allows an antivirus to be tested in everyday use before purchase.
It blocks them by behaviour if they are obfuscated. If they are not, it considers the scripts user-made and either blocks C&C server or IDP blocks secondary payload by behaviour. The script and the server will then be reported and blacklisted.McMcbrad,
Could you test AVG against scripting attacks? In my tests (trojan downloaders), AVG did not block almost anything (far worse than Norton). The files could be downloaded and run without problems. So, there is probably no additional script control in AVG.![]()
I can confirm that. I obfuscated the below script:It blocks them by behaviour if they are obfuscated. If they are not, it considers the scripts user-made and either blocks C&C server or IDP blocks secondary payload by behaviour. The script and the server will then be reported and blacklisted.
You don’t need to be sorry, as your topic is at the right place. Yes, the free version offers enough protection, specially if you increase heuristics sensitivity to max (as I do). It shows *some* alerts from time to time, but these are not so annoying and most people can live with them.@McMcbrad
do you consider the free version of avg as being enough in terms of protection, covering all sorts of malware types? file shield, web shield, ransomware shield, behaviour shield- are these shields enough to secure a novice user`s (let`s say my mom) laptop? is it a hassle free, install and forget antivirus? (i know we`re talking about the ultimate version here, sorry for the off topic)
I like it as a solution in the home environment. In fact, I was curious for a long time if any AV would adopt it for protection. Of course, it will not be sufficient in the targeted attacks.@Andy Ful
...
The more you over-complicate a solution, the more variable and fuzzy result it will produce for you. The proof is in Kaspersky Application Control and Norton Insight. They are expensive to execute and maintain, but they revolve around one very simple concept, where user should work only with trusted code and are both very effective.
Avast’s simple way of dealing with scripts is more than enough in a home environment.
The fileless Tesla I discovered is part of a targeted attack. PowerPoint presentation named “Wired Payment” with malicious Macro downloads an obfuscated JS script. The script in turn downloads another JS script, which downloads 2 PS scripts, ensuring their persistence(scheduled task and startup entry). The final payload is injected into msbuild.exe and cvtres.exe and is a version of Agent Tesla.I like it as a solution in the home environment. In fact, I was curious for a long time if any AV would adopt it for protection. Of course, it will not be sufficient in the targeted attacks.
To execute this script attacker will need to bypass execution policy so they will call PowerShell from another app (most likely *bat file CMD-> PowerShell) or Word/Excel. The attack chain will be suspended. Even if it’s not, final payload delivered via this method will look very suspicious to IDP and will be removed. I’ve tested it.I can use Base64 encoded script (trojan downloader) and it is allowed by AVG.
$base64="here is encoded script"
$a = [Text.Encoding]::Unicode.GetString([Convert]::FromBase64String($base64))
iex $a
So one can use obfuscated PowerShell script, encode it via Base64 and use the above script to bypass AVG.
Probably not if the script will inject the code filelessly. By allowing the scripting code, there are many ways to skirt around the heuristics, web shield, and behavior-based protection. So, AVG will have a hard time with fileless attacks. Of course, many such attacks will be detected and blocked, but many new ones will not.To execute this script attacker will need to bypass execution policy so they will call PowerShell from another app (most likely *bat file CMD-> PowerShell) or Word/Excel. The attack chain will be suspended. Even if it’s not, final payload delivered via this method will look very suspicious to IDP and will be removed. I’ve tested it.
In the event that you are patient 0 and everything has failed, ransomware shield and Password Protection shield can prevent exfiltration to some extent. They can also prevent encryption (if the purpose of the attack is to plant ransomware). So the overall harm will be reduced.Probably not if the script will inject the code filelessly. By allowing the scripting code, there are many ways to skirt around the heuristics, web shield, and behavior-based protection. So, AVG will have a hard time with fileless attacks. Of course, many such attacks will be detected and blocked, but many new ones will not.
The script execution policy can be easily bypassed in many ways. The simplest is via shortcut.
I freshly downloaded and installed AVG for a test.Unfortunately, Base64 encoding/decoding is commonly using by several kinds of malware. There is another possibility that can help. One can restrict PowerShell to Constrained Language Mode. This will prevent most of the advanced scripting methods, including Base64 encoding/decoding. It is applied in Windows built-in SRP, Applocker, and Application Control.![]()
In your case, 2 samples are blocked by the Web Shield (blacklisted URL detected). Others are blocked by detecting the command line (probably POwersheLL -w hidden -ENCOD is detected).I freshly downloaded and installed AVG for a test.
I grabbed few base-64 encoded strings and pasted them in PowerShell.
One of them triggered that:
View attachment 251659
Another one triggered that:
View attachment 251660
Third one triggered these 2 reactions:
View attachment 251661View attachment 251662
4th one:
View attachment 251663
The code starts with POwersheLL -w hidden -ENCOD
I suspected initially that that -w hidden might be the trigger, so I removed it, but the same detection occurs.
Not sure what distinguishes this in-the-wild malware from custom-based one.
Of course, blocking constrained language completely would be even more secure, but it doesn't look like Avast is inefficient.
I tried pasting this same code in scheduled task and shortcut, but the outcome is the same. Scheduled task gets deleted after detection.
View attachment 251665View attachment 251666View attachment 251667View attachment 251669
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -w hidden "-Command" "if((Get-ExecutionPolicy ) -ne 'AllSigned') { Set-ExecutionPolicy -Scope Process Bypass }; & 'c:\RunRemote\VBSObfuscator\encoded.ps1'"
It's good that attackers haven't yet discovered these methodsIt is also easy to use an innocent unobfuscated script (PowerShell or Windows Script Host) to run another script that uses obfuscated code encoded via Base64. This can be done from infected Pendrive or via packed email attachment (password protected). Anyway, in my tests, most AVs could be bypassed because they use only anti-script protection against very popular methods and there are many possibilities open to attackers.