bugün
- karısını puanlayıp sosyal medyada paylaşan erkek8
- kendinle sevgili olur muydun sorunsalı15
- 18 haziran 2026 yusuf ziya gümüşel'in tahliyesi4
- sivas divriğiye yerleşmek3
- karakalpakistan2
- kilo verdiren gıda4
- vedat muriqi3
- linkedin4
- izinli yazarın entry girebilmesi6
- ismail kartal10
- sözluk kız ayarlama yeri değildir12
- yıllık yazısı3
- org vs synthesizer4
- tripofobisi olanlar revani yemezler4
- hiçbir kızın senden hoşlanmaması8
- azizlik neden ispanyollara mahsus5
- insan sanatsal bir varlıktır8
- beşar esad vs kemal kılıçdaroğlu3
- fenerbahçede dördüncü ismail kartal dönemi10
- koyun yoğurdu3
- sözlük yazarlarına gelen son mesaj2
- islam düşmanlarına epstein şoku12
- 2026 dünya kupası13
- asansörde kalmak2
- yaş ilerledikçe anlaşılan şeyler8
- 18 haziran 2026 moskova drone saldırısı2
- iş verenlerin aç gözlü olması11
- gecenin şarkısı5
- sokak röportajı veren sıradan vatandaş2
- kemal derviş5
- ulukışla2
- çiftehan2
- bugün ne yedin10
- kaslı erkeklerin gizli ruh hastası olması4
- sistem patlamış4
- şu anda ne yapıyorsun19
- en iyi yanık kremi5
- ortalama bir insan olmak2
- egay sucukcu7
- bir gün ölecek olmak6
- böceği öldürmek yerine dışarı atan insaflı kişi8
- en iyi terapi6
- sokaktaki çocuk sesleri4
- aydın da bir tonluk balyanın altında kalan adam2
- yanlış mesleği seçtim denilen an5
- çekya2
- 9000 iş günü prim ödemek2
- yanlışlıkla erkek sikmek8
- kemal kılıçdaroğlu12
- kademeli emeklilik sistemi2
türkiyeye mesaj gönderdikten 3 saat sonra hacklendiler bide utanmadan nedenini yazmışlar buyrun:
Here are some facts about what happened to anonops.com today:
First off lets start with the reassurance that nothing off ours was compromised, not at all. In no way were any systems that are owned by us hacked, defaced, nuked, etc. This is a guarantee. Do not be fooled by people who are too incompetent to understand what actually happened, or the psyops that want to drive you away from the network.
What really happened was a hijacking of our DNS for the domain anonops.com. Basically someone seems to be introducing a rogue SOA record for our domain, that is pointing to their name servers. Beyond the fact that there is a rogue SOA being introduced we are unsure how the attacker is managing this. It is entirely possible that a rogue registrar is assisting him, or was compromised to allow him to do this. This is sadly beyond our control.
Lets use our friend dig, you can try this from your own box if you like, to verify my claims:
;; QUESTION SECTION:
;anonops.com. IN SOA
;; ANSWER SECTION:
anonops.com. 80371 IN SOA leah.ns.cloudflare.com. dns.cloudflare.com. (
2013060215 ; serial
10000 ; refresh (2 hours 46 minutes 40 seconds)
2400 ; retry (40 minutes)
604800 ; expire (1 week)
3600 ; minimum (1 hour)
)
Fantastic! This is what our SOA is supposed to be, let me query again though.
;; QUESTION SECTION:
;anonops.com. IN SOA
;; ANSWER SECTION:
anonops.com. 84853 IN SOA garfi1.militanz.com. zvorleyfunky.mail.com. (
2013060302 ; serial
86400 ; refresh (1 day)
7200 ; retry (2 hours)
3600000 ; expire (5 weeks 6 days 16 hours)
86400 ; minimum (1 day)
)
Oh noes! This is not our SOA. Querying the same thing withing 5 seconds returns a different result, there is two SOA's being propogated for our domain, our legit one, and the rogue one. Again, feel free to try this for yourself.
So what does this all mean?
This means that at the moment any records that you retrieve from the anonops.com domain will not be legitimate. It is possible for the attacker to redirect you to wherever he wants to, and gather your IP.
If you want to connect to our IRC, use a direct IP: 199.59.161.30.
Sadly, this shows just how flawed the DNS system is, and how even if your servers are secure, you can get screwed by a third party.
Here are some facts about what happened to anonops.com today:
First off lets start with the reassurance that nothing off ours was compromised, not at all. In no way were any systems that are owned by us hacked, defaced, nuked, etc. This is a guarantee. Do not be fooled by people who are too incompetent to understand what actually happened, or the psyops that want to drive you away from the network.
What really happened was a hijacking of our DNS for the domain anonops.com. Basically someone seems to be introducing a rogue SOA record for our domain, that is pointing to their name servers. Beyond the fact that there is a rogue SOA being introduced we are unsure how the attacker is managing this. It is entirely possible that a rogue registrar is assisting him, or was compromised to allow him to do this. This is sadly beyond our control.
Lets use our friend dig, you can try this from your own box if you like, to verify my claims:
;; QUESTION SECTION:
;anonops.com. IN SOA
;; ANSWER SECTION:
anonops.com. 80371 IN SOA leah.ns.cloudflare.com. dns.cloudflare.com. (
2013060215 ; serial
10000 ; refresh (2 hours 46 minutes 40 seconds)
2400 ; retry (40 minutes)
604800 ; expire (1 week)
3600 ; minimum (1 hour)
)
Fantastic! This is what our SOA is supposed to be, let me query again though.
;; QUESTION SECTION:
;anonops.com. IN SOA
;; ANSWER SECTION:
anonops.com. 84853 IN SOA garfi1.militanz.com. zvorleyfunky.mail.com. (
2013060302 ; serial
86400 ; refresh (1 day)
7200 ; retry (2 hours)
3600000 ; expire (5 weeks 6 days 16 hours)
86400 ; minimum (1 day)
)
Oh noes! This is not our SOA. Querying the same thing withing 5 seconds returns a different result, there is two SOA's being propogated for our domain, our legit one, and the rogue one. Again, feel free to try this for yourself.
So what does this all mean?
This means that at the moment any records that you retrieve from the anonops.com domain will not be legitimate. It is possible for the attacker to redirect you to wherever he wants to, and gather your IP.
If you want to connect to our IRC, use a direct IP: 199.59.161.30.
Sadly, this shows just how flawed the DNS system is, and how even if your servers are secure, you can get screwed by a third party.
Gündemdeki Haberler
Güncel Önemli Başlıklar