Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False Positive | tobagency.com #1039

Open
alexis-tob opened this issue Jan 20, 2025 · 1 comment
Open

False Positive | tobagency.com #1039

alexis-tob opened this issue Jan 20, 2025 · 1 comment
Assignees

Comments

@alexis-tob
Copy link

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

  • tobagency.com
  • blog.tobagency.com
  • info.tobagency.com
  • quotes.tobagency.com

Why do you believe this is a false-positive?

We completely rebuilt our website in a different host and redesigned and built our website from scratch after malicious content was detected.
New security policies were implemented, users and their roles/permissions were audited and updated across the site. We believe the website is no longer a threat.

More details:

  • Migrated from Wordpress to HubSpot CMS
  • Developed every single asset from scratch (JS and CSS)

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

Website was hacked

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

VirusTotal

Have you requested a review from other sources?

I have requested reviews from CRDF, Symantec; and according to PhishTank nothing is known about the site.

Do you have a screenshot?

Screenshot

Additional Information or Context

I have also noticed that...

@phishing-database-bot
Copy link
Member

Verification Required

@alexis-tob, 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-0693bfdc4f14b27df0c5cf05f5ccb8f3af9753c7

    Your Verification ID: antiphish-0693bfdc4f14b27df0c5cf05f5ccb8f3af9753c7

  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 [email protected] - 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:

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

The Phishing.Database Project Team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

6 participants