Page 1 of 1

IRC.Supernets.org

Posted: Tue Nov 21, 2023 11:36 pm
by RenSHosting
a few days now there wil be created akills on my server with the following content:
11[23:37:57] 0[4RenS-Chat0][12notice.11OperServ0] <OperServ0> 3 *@*.nl [Sabine] /!\ WARNING /!\ This channel has moved to IRC.SUPERNETS.ORG
11[23:37:57] 0[4RenS-Chat0][12notice.11OperServ0] <OperServ0> 4 *@*.be [Sabine] /!\ WARNING /!\ This channel has moved to IRC.SUPERNETS.ORG
11[23:37:57] 0[4RenS-Chat0][12notice.11OperServ0] <OperServ0> 5 *@*.com [Sabine] /!\ WARNING /!\ This channel has moved to IRC.SUPERNETS.ORG
11[23:37:57] 0[4RenS-Chat0][12notice.11OperServ0] <OperServ0> 6 *@*.de [Sabine] /!\ WARNING /!\ This channel has moved to IRC.SUPERNETS.ORG
11[23:37:57] 0[4RenS-Chat0][12notice.11OperServ0] <OperServ0> 7 *@*.org [Sabine] /!\ WARNING /!\ This channel has moved to IRC.SUPERNETS.ORG
11[23:37:57] 0[4RenS-Chat0][12notice.11OperServ0] <OperServ0> 8 *@*.net [Sabine] /!\ WARNING /!\ This channel has moved to IRC.SUPERNETS.ORG
11[23:37:57] 0[4RenS-Chat0][12notice.11OperServ0] <OperServ0> 9 *@*.fi [Sabine] /!\ WARNING /!\ This channel has moved to IRC.SUPERNETS.ORG
11[23:37:57] 0[4RenS-Chat0][12notice.11OperServ0] <OperServ0> 10 *@*.no [Sabine] /!\ WARNING /!\ This channel has moved to IRC.SUPERNETS.ORG
11[23:37:57] 0[4RenS-Chat0][12notice.11OperServ0] <OperServ0> 11 *@*.la [Sabine] /!\ WARNING /!\ This channel has moved to IRC.SUPERNETS.ORG
11[23:37:57] 0[4RenS-Chat0][12notice.11OperServ0] <OperServ0> 12 *@*.io [Sabine] /!\ WARNING /!\ This channel has moved to IRC.SUPERNETS.ORG

My oper was gone away to sleep when this was happend. Please advise me what i can do to this.

Re: IRC.Supernets.org

Posted: Tue Nov 21, 2023 11:41 pm
by RenSHosting
the also use al my other ircop user names to set the akill list.

Re: IRC.Supernets.org

Posted: Wed Nov 22, 2023 12:11 am
by Jellis
We had clients who have IRC servers running being infected with some kind of trojan and their ZNC / Services access passwords continue to get compromised seeing the same behavior you are reporting, we figured this out fairly quickly and we disabled all oper access and services access to the affected opers. After recommending those opers to reinstall their computer without any cracks and other illegal and outdated software mess the attacks stopped when given access again on the IRC networks.

Hope this helps!