Potassium · País
Ataques observados — Luxemburgo
Luxemburgo: observações de ataques do Potassium que afetam redes locais — prefixos atacados, operadoras afetadas, métodos e datas dos últimos 30 dias.
46 observações · Últimos 30 dias · Última observação
Redes mais afetadas
Últimos 30 dias
Métodos mais observados
Últimos 30 dias
Observações recentes
- UDP datagram flood, variant 7202.78.161.128/32UDP/801mLuxemburgo
- UDP datagram flood, variant 7202.78.161.128/32UDP/532mLuxemburgo
- UDP datagram flood, variant 7202.78.161.128/32UDP/531mLuxemburgo
- UDP datagram flood, variant 7202.78.161.128/32UDP/531mLuxemburgo
- UDP datagram flood, variant 7193.239.179.18/32UDP/255652mLuxemburgo
- UDP datagram flood, variant 7202.78.161.128/32UDP/531mLuxemburgo
- Mixed TCP/UDP flood202.78.161.128/32TCP/UDP/2230sLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/210658sLuxemburgo
- TCP connection flood193.239.179.145/32TCP/210658sLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- UDP datagram flood, variant 7202.78.161.128/32UDP/5330sLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21062mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21062mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21062mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21062mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21062mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21062mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21062mLuxemburgo
- TCP connection flood193.239.179.145/32TCP/21061mLuxemburgo
O botnet.cl relata a infraestrutura que observou. Um endereço que aparece aqui identifica um alvo ou um relay, não uma pessoa responsável pelo ataque.