indexer: notabug.io
all comments

[]Chungus -0 points

[]x0x7 -0 points

The benefit of being on node js and running a reverse proxy. I just take everything with goes for php and has the ip address as the host and put it on a hang list.

Ok, I also make sure admin is mentioned someone in at least one of the urls and that no legitimate traffic is coming from that ip. But after that it's.

var badip = ['103.1.43.193','104.248.26.88','111.2.28.153','116.196.21.26','116.92.226.146','118.24.42.53','118.25.91.180','118.26.140.110','118.89.48.223','119.29.2.128','119.29.24.10','119.29.66.202','122.114.5.200','123.207.84.50','123.58.3.39','124.173.64.175','125.227.124.79','132.232.75.79','139.199.100.64','139.199.15.51','14.63.165.157','147.156.179.50','174.138.57.223','192.144.175.67','198.167.223.52','210.26.98.69','212.237.0.99','219.138.105.186','35.225.175.153','47.93.117.4','50.254.129.69','81.202.35.237','92.87.91.22','93.46.124.95','94.191.42.89'];
badip = new Set(badip);

var hanglist = [];
var hanglimit = 25;
(req,res)=>{
 var ip = req.connection.remoteAddress.replace('::ffff:','');
 if(!importantip.has(ip) && badip.has(ip)) {
  hanglist.push(res);
  if(hanglist.length>hanglimit) {
   hanglist.forEach(i=>i.end());
   hanglist = [];
  }
  return;
 }
 //more code
});

Maybe that's not the best way to handle bad traffic but I'm willing to eat some cost in the form of pooled connections to slow them down.

[] -0 points

The issue is, if you're going to add to this list automatically, you run the risk of banning legitimate traffic when the IP is shared. This may or may not be a big issue.

I've run sites in the past where everything with a chinese or russian IP doesn't even get a response (so the server is effectively not there). That stops via obscurity most attacks because they're often just going for low hanging fruit.

[] -0 points

just ban them ffs

π