False Positive | www.amazon.com

[nextwavepublish]

What are the subjects of the false-positive (domains, URLs, or IPs)?

www.amazon.com
amazon.com

Why do you believe this is a false-positive?

I believe this is a false-positive because this is a very popular website and not malware.

How did you discover this false-positive(s)?

VirusTotal

Where did you find this false-positive if not listed above?

Virustotal. https://www.virustotal.com/gui/domain/www.amazon.com?nocache=1

Have you requested a review from other sources?

Do you have a screenshot?

Yes

Additional Information or Context

No response

[phishing-database-bot]

Verification Required

@nextwavepublish, thank you for submitting a false positive report! To help us verify your ownership of the affected domain(s), please complete the following steps:

1. Set a DNS TXT record for the domain(s) listed in this issue with the following details:

   • Record Name: _phishingdb
   • Record Value: antiphish-b533ca62c49fe008627040605bd608473fc8be96

   Your Verification ID: antiphish-b533ca62c49fe008627040605bd608473fc8be96

2. Wait for DNS propagation (this may take a few minutes to a few hours).

3. Reply to this issue once the TXT record has been set.

Important Notes

• Verification does not guarantee whitelisting. The Phishing.Database team will review your report after verifying ownership, but the decision to whitelist depends on further investigation and analysis.
• If the record cannot be set or you need alternative methods of verification, please contact us at contact@phish.co.za - preferably from the domain's official email address.

How to Check the TXT Record ?

You can verify that the TXT record is properly set using:

• Online tools like MXToolBox TXT Lookup.
• The command line:

  dig TXT _phishingdb.example.com
  

Thank you for your cooperation! We will address your issue as soon as possible after verification.

The Phishing.Database Project Team.

[nextwavepublish]

This is not my domain. It is amazon.com.

[nextwavepublish]

@spirillen @mitchellkrogza @funilrys @g0d33p3rsec Following up on this

[nextwavepublish]

@spirillen @mitchellkrogza @funilrys @g0d33p3rsec Following up on this

[spirillen]

Hey @nextwavepublish! Just wanted to give you a quick update on why I haven’t been able to tackle this issue. It turns out that Amazon (AWS) is on a different whitelist that this project uses. Plus, I’ve been a bit out of it lately because of my cataract troubles. Really appreciate the coffee, though! ☕

So, it looks like the whitelist system is acting up again, and I don’t have the keys to get into the backend and sort it out.

I’ve reopened the issue here: https://github.com/Phishing-Database/phishing/issues/749. Now we just need to wait for funilrys to check it out since he’s the only one with the keys. 🤷🏻

Cheers!

[nextwavepublish]

Hey @nextwavepublish! Just wanted to give you a quick update on why I haven’t been able to tackle this issue. It turns out that Amazon (AWS) is on a different whitelist that this project uses. Plus, I’ve been a bit out of it lately because of my cataract troubles. Really appreciate the coffee, though! ☕

So, it looks like the whitelist system is acting up again, and I don’t have the keys to get into the backend and sort it out.

I’ve reopened the issue here: https://github.com/Phishing-Database/phishing/issues/749. Now we just need to wait for funilrys to check it out since he’s the only one with the keys. 🤷🏻

Cheers!

I appreciate the follow up! Yeah I noticed Amazon.com is already on the whitelist but for some reason www.amazon.com triggers a flag on Virustotal.

Sorry to hear about the cataracts, that really sucks. Well, guess nothing to do but wait for funilrys then. Thanks again!