Potassium · País
Ataques observados — Singapura
Singapura: observações de ataques do Potassium que afetam redes locais — prefixos atacados, operadoras afetadas, métodos e datas dos últimos 30 dias.
119 observações · Últimos 30 dias · Última observação
Redes mais afetadas
- OVH SASAS1627632
- Telegram Messenger IncAS6201424
- VibeGAMES B.V.AS4892510
- Akamai Connected CloudAS639499
- Alibaba (US) Technology Co., Ltd.AS451025
- Tencent Building, Kejizhongyi AvenueAS1322035
- Cloudflare, Inc.AS133354
- Google LLCAS151693
Últimos 30 dias
Métodos mais observados
- UDP datagram flood, variant 777
- TCP connection flood24
- UDP payload flood13
- UDP datagram flood, variant 134
- UDP datagram flood, variant 121
Últimos 30 dias
Observações recentes
- UDP datagram flood, variant 751.79.209.105/32UDP/77971mSingapura
- UDP payload flood35.213.168.168/32UDP/05mSingapura
- UDP datagram flood, variant 751.79.209.105/32UDP/77971mSingapura
- UDP datagram flood, variant 751.79.209.109/32UDP/77771mSingapura
- UDP datagram flood, variant 751.79.163.179/32UDP/270151mSingapura
- UDP datagram flood, variant 7136.85.43.128/32UDP/533m 19sSingapura
- UDP datagram flood, variant 735.213.168.168/32UDP/533m 19sSingapura
- TCP connection flood103.170.217.245/32TCP/801mSingapura
- UDP datagram flood, variant 747.84.148.166/32UDP/200371mSingapura
- UDP datagram flood, variant 715.235.174.97/32UDP/77772mSingapura
- UDP datagram flood, variant 791.108.17.23/32UDP/3200330sSingapura
- TCP connection flood103.170.217.245/32TCP/801mSingapura
- TCP connection flood103.170.217.245/32TCP/801mSingapura
- UDP datagram flood, variant 1340.27.47.155/32UDP/301202mSingapura
- UDP datagram flood, variant 715.235.174.97/32UDP/77772mSingapura
- TCP connection flood159.223.55.94/32TCP/221mSingapura
- UDP datagram flood, variant 751.79.163.179/32UDP/270151mSingapura
- UDP datagram flood, variant 12136.85.43.128/32UDP/533m 19sSingapura
- UDP datagram flood, variant 751.79.163.179/32UDP/270151mSingapura
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapura
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapura
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapura
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapura
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapura
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapura
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapura
- TCP connection flood15.235.174.103/32TCP/144001mSingapura
- UDP payload flood185.214.125.159/32UDP/4432m 29sSingapura
- TCP connection flood15.235.174.103/32TCP/144001mSingapura
- UDP datagram flood, variant 7209.25.142.22/32UDP/12111mSingapura
- UDP datagram flood, variant 735.213.168.168/32UDP/533m 19sSingapura
- UDP payload flood185.214.125.159/32UDP/4432m 29sSingapura
- TCP connection flood15.235.174.103/32TCP/144001mSingapura
- TCP connection flood47.84.67.250/32TCP/4431mSingapura
- TCP connection flood47.84.67.250/32TCP/4431mSingapura
- TCP connection flood47.84.67.250/32TCP/4431mSingapura
- UDP payload flood185.214.125.159/32UDP/4432m 29sSingapura
- TCP connection flood43.159.18.113/32TCP/143011mSingapura
- TCP connection flood43.159.18.115/32TCP/143011mSingapura
- TCP connection flood43.159.18.115/32TCP/143011mSingapura
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.