Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://social.wildeboer.net/users/jwildeboer/statuses/116832567702010267">Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Tuesday, 30-Jun-2026 03:36:12 JST</a><a href="https://social.wildeboer.net/@jwildeboer" title="jwildeboer@social.wildeboer.net"><img src="https://gnusocial.jp/avatar/2767-48-20251201222121.webp" width="48" height="48" alt="Jan Wildeboer 😷:krulorange:" style="position: absolute; left: 0; top: 0;">Jan Wildeboer 😷:krulorange:</a><div><a href="https://lighthouse.co.im/@alan/116832411918631647" rel="in-reply-to">in reply to</a><ul><li></ul></div></section><article><p><a href="https://lighthouse.co.im/@alan">@alan</a> These botnets are more or less immune to rate limiting, as they use many (and I mean millions) of IP addresses fro a run and each IP address is only used for a few requests before it is being put back in the queue. The IP addresses are also from many different providers, so a (sub-)net wide block also doesn't help. I wrote about those "residential IP proxies in [1] and [2].</p><p>[1] <a href="https://jan.wildeboer.net/2025/02/Blocking-Stealthy-Botnets/" rel="nofollow">https://jan.wildeboer.net/2025/02/Blocking-Stealthy-Botnets/</a><br>[2] <a href="https://jan.wildeboer.net/2025/04/Web-is-Broken-Botnet-Part-2/" rel="nofollow">https://jan.wildeboer.net/2025/04/Web-is-Broken-Botnet-Part-2/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/6513349#notice-12817573">In conversation</a><time datetime="2026-06-30T03:36:12+09:00" title="Tuesday, 30-Jun-2026 03:36:12 JST">about 2 months ago</time> <span>from <span><a href="https://social.wildeboer.net/@jwildeboer/116832567702010267" rel="external" title="Sent from social.wildeboer.net via ActivityPub">social.wildeboer.net</a></span></span><a href="https://social.wildeboer.net/@jwildeboer/116832567702010267">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: jan.wildeboer.net</div><h5><a href="https://jan.wildeboer.net/2025/04/Web-is-Broken-Botnet-Part-2/">Botnet Part 2: The Web is Broken</a></h5><div></div></header><div>I guess you have all heard about the growing problem of AI companies trying to aggressively collect whatever data they can get their hands on to train their models. This has caused an explosive surge in web crawlers relentlessly hitting servers big and small. But who runs these crawlers? Turns out — it could be you!</div><footer></footer></article></li><li><article><header><div>Domain not in remote thumbnail source whitelist: jan.wildeboer.net</div><h5><a href="https://jan.wildeboer.net/2025/02/Blocking-Stealthy-Botnets/">Botnet Part 1: Those Stealthy Botnets</a></h5><div></div></header><div>It’s one of those days again where botnets are hammering my little e-mail server with brute force attacks to send spam. This comes in waves, but is persistent and part of the #SysAdminLife. (They obviously fail ;)</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Tuesday, 30-Jun-2026 03:36:12 JSTJan Wildeboer 😷:krulorange:
in reply to
- al
@alan These botnets are more or less immune to rate limiting, as they use many (and I mean millions) of IP addresses fro a run and each IP address is only used for a few requests before it is being put back in the queue. The IP addresses are also from many different providers, so a (sub-)net wide block also doesn't help. I wrote about those "residential IP proxies in [1] and [2].
[1] https://jan.wildeboer.net/2025/02/Blocking-Stealthy-Botnets/
[2] https://jan.wildeboer.net/2025/04/Web-is-Broken-Botnet-Part-2/
In conversationabout 2 months ago from social.wildeboer.netpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: jan.wildeboer.net
  Botnet Part 2: The Web is Broken
  I guess you have all heard about the growing problem of AI companies trying to aggressively collect whatever data they can get their hands on to train their models. This has caused an explosive surge in web crawlers relentlessly hitting servers big and small. But who runs these crawlers? Turns out — it could be you!
2. Domain not in remote thumbnail source whitelist: jan.wildeboer.net
  Botnet Part 1: Those Stealthy Botnets
  It’s one of those days again where botnets are hammering my little e-mail server with brute force attacks to send spam. This comes in waves, but is persistent and part of the #SysAdminLife. (They obviously fail ;)

Public

Embed Notice

HTML Code

Corresponding Notice