bugün
- mohamed salah'ın trabzonspor'a transferi5
- 2026 ağustos ayının serin geçmesi3
- insanlar sizi nasıl tanımlar7
- duş almak vs duş yapmak5
- meal kuran değildir26
- 5 ağustos 20263
- geceye güzel bir söz bırak6
- online kumar3
- dinamo zagreb'in kauno zalgiris'i 5 0 yenmesi3
- gecenin film sahnesi5
- bir erkek ve bir kız arkadaş olabilir mi13
- dürüm yerken uzaklara dalmak3
- bayan kelimesi neden rahatsız edici28
- aslan abilerim sözlüğe geri dönsün kampanyası7
- acil iş fikri lazım arkadaşlar16
- lionel messi2
- iremga12
- çoğu yazarları donuzlamış olmam7
- afrika nasıl kalkınabilir15
- polonya2
- bella hadid5
- velvet almanyaya gel5
- imamoğlu'nun tutukluluğunun 100 günü16
- mohamed salah ghaly5
- trabzonspor harbiden salah'ı almış4
- kendini anlatamamak6
- velvet14
- kız arkadaş kiralamak7
- fakir olduğu halde bir erkeğe aşık olmak3
- ıban at4
- kahve falı3
- yazarlara sözlüğü zehir zıkkım etmek4
- sözlükte erkek yazar istemiyoruz kampanyası4
- arkadaşlar bakar mısınız9
- halit bolkan2
- gürkan uygun3
- 31 çekerken eli kırmak3
- birinin size söylediği en kırıcı şey nedir6
- kendine 10 üzerinden kaç verirsin4
- geceye 90 lardan bir şarkı bırak4
- dünya sivaslılar günü3
- 3 ağustos 2026 aykolik gocu buluşması19
- had bildirmek6
- yunanistan30
- uzak diyar nickli gurbetçi akp li3
- uzak diyar4
- tai lung7
- lulu3
- arkadaşlar ben başaramadım3
- turşunun iyisi limonla mı sirkeyle mi11
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