101–110 of 310 posts
Earlier quoted context omitted.
Seems like it would be fairly easy to use this pseudo selector, and apply it to every element on the page. Making them show up as empty to the user
You could add a data attribute to the html tag of the document with the current URL, I.E. then hide the full page with: html {display: none;} html[data-path*="saashub.com"] {display:block;}
What about a slightly alternative approach, where instead of trying to block the abuser, you try to make it clear to end users what the real website is? E.g. in your logo image, include the real domain name "saashub.com". Have some introduction text on your home page "Here at saashub.com, we compare SaaS products ...." When your images are hotlinked, replace them with text like "This is a fraudulent website, find us…
> 4) Use absolute URLs everywhere - they are rewriting everything www.saashub.com to their domain name.
Earlier quoted context omitted.
You could add a data attribute to the html tag of the document with the current URL, I.E. then hide the full page with: html {display: none;} html[data-path*="saashub.com"] {display:block;}
This seems quite elegant and easy. Obviously in addition to other measures, but I like it.
Put brandings/personalizations/signatures in your pages that are not easy to remove to remove automatically. Include your site URL if possible. The idea is that if a visitor sees these on a different site, it becomes obvious that the content doesn't belong there.
Write an article page about these things happening, specifically mentioning the mirroring site URLs, and see if they will also blindly mirror it.
Earlier quoted context omitted.
For 2) you mean you loaded it from the adversary's proxy site, just to clarify?
Yes, constructed the honeypot URL using the proxy site and called it (thousands of times) so I can get them to fetch it from my server through their IP so I can log it.
Also: since you say 4k-5k IPs... any of them from cloud providers? And specific location?
- "bait urls" that other crawlers won't touch
- trigger by request volume and filter out legit crawlers
- find something unique about the headers in their requests that you can identify them with
Another idea is to serve them something that you can then report as some type of violation to Google, or something (think SafeSearch) that gets their site filtered.
Instead, plot a few different changes and throw them in all at once. Preferably in a way where they will have to solve all of the changes at the same time to figure out what happened and get things working again. Also, favor changes that are harder to detect. E.g., pure IP blocks are easier to detect than tarpitting and returning fake/corrupted content. The longer their feedback loops, the more likely it is that they'll just give up and go be a parasite somewhere else.
You're already using Cloudflare, you could try talking to their support or just turning up settings to make it more strict for bots.
What about a slightly alternative approach, where instead of trying to block the abuser, you try to make it clear to end users what the real website is? E.g. in your logo image, include the real domain name "saashub.com". Have some introduction text on your home page "Here at saashub.com, we compare SaaS products ...." When your images are hotlinked, replace them with text like "This is a fraudulent website, find us…
Not sure if this would help since: > 4) Use absolute URLs everywhere - they are rewriting everything www.saashub.com to their domain name.