TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

How to deal with bogus security reports?

1 pointsby ruikover 4 years ago
We started to receive a lot of questionable security reports to our security@domain mail. All are from India, all use gmail addresses. Usually they claim that there is no DMARC (but they did not bother to check SPF). Or they get 302 from our server and use &lt;!DOCTYPE HTML PUBLIC &quot;-&#x2F;&#x2F;IETF&#x2F;&#x2F;DTD HTML 2.0&#x2F;&#x2F;EN&quot;&gt; to claim: &quot;The information can be used by attackers for further finding of exploits and information gathering.&quot;<p>They are partly like scams, but reporting them to google gmail did not help. Any clue?

1 comment

lrvickover 4 years ago
Every bug program I have had any exposure to is mostly reports like these.<p>Once I started insisting researchers PGP encrypt their submissions to prevent leaks of potentially serious and sensitive issues... A side effect was it was easy to tell authentic reports from skiddy stuff.<p>No one with any significant security research experience has been able to avoid learning basic asymmetric cryptography... But the skiddies only want to copy paste from automated tools to hunt easy bounties.