05.15
We have found a leak-Site on there a User have posted a Mail from hideme.ru.
Original:
Translated via google to English:
You can see, that he list BlockList.de to one of the Blacklist which the User does not insert there VPN-IP 🙂
We hope our service makes the Internet better, safer and helps to clean the infected PCs.
We have found a leak-Site on there a User have posted a Mail from hideme.ru.
Original:
Translated via google to English:
You can see, that he list BlockList.de to one of the Blacklist which the User does not insert there VPN-IP 🙂
In earlier Posts we have write over nobistech AS15003 here:
We see a long time that only Squid-Proxys (Version from 3.1.4 to 3.1.9) with SSH on the
Port 2382
and with the Domain ipvnow.com with no sites (linked to a enom-buy-site) in the Reverse-DNS….
We have 1,406 Records to IPs with the rdns hase ipvnow.com in the host.
262 with ns0.ipvnow.com
We think the Customer behind is the User „keliix06“.
We have send to abuse AT nobistech.net only for the last 8 Days ~500 Reports and we send only all 24 hours for each ip/attack one report…
Now, we have blocked the complete IP-Range permantly:
173.234.225.0 – 173.234.227.255
in the all-Export-List and in the RBL.
We have informed nobistech too in the same time we public this article.
Ein kurzes aktivieren der Logs auf einem der mittlerweile 4 RBL-Server hat gezeigt, das in 2 Minuten mehreer hundert unterschiedliche (unique) IP-Adressen (hauptsächlich DNS-Server) die RBL-Listen von blocklist.de abfragen.
Je nach Liste, welche nach Service-Diensten/Arten aufgesplittet sind, umfassen diese im Durschnitt über 6.000 IP-Adressen.
Wie man die RBL-Listen von blocklist z.B. selbst im Postfix, Amavis, Policyd oder Apache einsetzten kann ist unter folgender URL im Forum beschrieben:
https://forum.blocklist.de/viewtopic.php?f=11&t=17
Aktuell unterstüzten die RBL-Server noch kein IPv6, da müssen wir auf Updates vom Hersteller warten.
Bei Fragen, Anregungen oder Wünschen einfach ins Forum posten 😉
After our last notice we have build a new Check after the „normal“ Whitelist and other Checks.
Now, we look into the DNSBL from sectoor.de and exitlist.torproject.org for the spaming IP, when the Attack-Typ is RegBot or BadBot.
When the Tor-Server is in the dnsbl, but not in our Whitelist we received a notification to check the Tor-Server and block them permanently from our Honeypot-systems or whitelist them.
This make the way from tor-Server-Admins easier.