Amazon blocked

[xraiderv18]

also, as of this morning...

Email response from Avast this morning:

Hello,

Thank you for reporting this false positive.

Our virus specialists have now cleared its reputation in our database.

With URLs this change should be instant, but it might take up to 24 hours with files.

For future reference you might also find the following article to be useful:  <Link: https://support.avast.com/en-us/article/228/> Avast Clean Guidelines.


Best regards,

Avast Customer Care

However, Avast is still flagging Amazon, even though I tried to update the definitions (it said it was already up to date: v210621-2). I guess I'll just whitelist that specific cloudfront.net URL for awhile and then test it later today or tomorrow with the whitelist removed.

Also, while VirusTotal.com showed no flags when I entered the cloudfront URL late last night, a few hours later the same website showed that Comodo Valkyrie Verdict was flagging the URL as malware (maybe their employees read this forum? ).

as reported in this thread https://forum.avast.com/index.php?topic=284118.msg1629518#msg1629518

I was right. false positive.

to quote so many video games and boardwalk crane games: thank you for playing, please try again.

[DavidR]

also, as of this morning...

also, as of this morning...
<snip quote>
However, Avast is still flagging Amazon, even though I tried to update the definitions (it said it was already up to date: v210621-2). I guess I'll just whitelist that specific cloudfront.net URL for awhile and then test it later today or tomorrow with the whitelist removed.

Also, while VirusTotal.com showed no flags when I entered the cloudfront URL late last night, a few hours later the same website showed that Comodo Valkyrie Verdict was flagging the URL as malware (maybe their employees read this forum? ).

as reported in this thread https://forum.avast.com/index.php?topic=284118.msg1629518#msg1629518

I was right. false positive.
<snip>

I can only assume that you didn't submit it as a possible false positive.

I did submit it to avast as a possible false positive (so it could be investigated) and I too got the same email response from the virus labs team.

False positive or not it isn't something that should be assumed, adding it as an exception (at your own risk) and or submit is as a possible false positive.

[xraiderv18]

actually..once I was aware of the reporting tool for false positives, thats EXACTLY what I did, I submitted a report.

under siege 2 dark territory, that maxim about assumptions.

[DavidR]

actually..once I was aware of the reporting tool for false positives, thats EXACTLY what I did, I submitted a report.

under siege 2 dark territory, that maxim about assumptions.

In the absence of information it is easy to make an 'ass' out of 'u' and 'me'

[Muad'Dib]

Why is it so hard to figure out that if you go to https://www.amazon.com/ there is no problem or blockage?

Because different people experience different results (see my results below).

[xraiderv18]

actually..once I was aware of the reporting tool for false positives, thats EXACTLY what I did, I submitted a report.

under siege 2 dark territory, that maxim about assumptions.

In the absence of information it is easy to make an 'ass' out of 'u' and 'me'

actually, in the movie..the response was 'did you see a body? assumption is the mother of all frakkups' 

[DavidR]

Why is it so hard to figure out that if you go to https://www.amazon.com/ there is no problem or blockage?

Because different people experience different results (see my results below).

Ensure that you have updated the virus definitions and possibly clear your browser cache.

[Muad'Dib]

Why is it so hard to figure out that if you go to https://www.amazon.com/ there is no problem or blockage?

Because different people experience different results (see my results below).

Ensure that you have updated the virus definitions and possibly clear your browser cache.

My definitions are updated to the latest (as of this posting, 210621-2), and the problem occurred on multiple browsers (with cache cleared on all). Besides, as I stated in a related post, Avast confirmed this morning that this was a false positive.

I was simply pointing out that just because some users aren't experiencing the problem, this doesn't mean there isn't a problem.

[xraiderv18]

how does the web shield function anyways? whats the exact operating method...

[DavidR]

@  Muad'Dib
I honestly can't see if it has been confirmed as an False Positive (I reported it also even though I never got the alert) and as the reply email states.
"With URLs this change should be instant, but it might take up to 24 hours with files."

So I can't understand why you are still getting the alert and is it the same (e.g. the xxxxxxxx.cloudfront.com one) ?

[slsl6]

Bob--

Obviously something is going on since I and others are being blocked.

[bob3160]

Bob--

Obviously something is going on since I and others are being blocked.

Others in this case are a very small group so the question is what are you running that's causing it that the rest of us are not?

[xraiderv18]

the differences here come down to individual software environments I suspect, which is why some were, and some were not, seeing this problem.

[slsl6]

Bob--

You don't know the exact number of people involved. But I doubt it's one or two. Just because it's not happening to you doesn't make it wrong.

[slsl6]

Just gave it a test and I could log in. So thanks to either the Amazon or Avast teams for clearing it up!