Potassium 路 Country
Attacks observed in Singapore
Potassium attack observations affecting networks in Singapore: targeted prefixes, affected operators, attack methods, and timing over the last 30 days.
119 observations 路 Last 30 days 路 Latest observation
Most affected networks
- 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
Last 30 days
Most observed methods
- UDP datagram flood, variant 777
- TCP connection flood24
- UDP payload flood13
- UDP datagram flood, variant 134
- UDP datagram flood, variant 121
Last 30 days
Recent observations
- UDP datagram flood, variant 751.79.209.105/32UDP/77971mSingapore
- UDP payload flood35.213.168.168/32UDP/05mSingapore
- UDP datagram flood, variant 751.79.209.105/32UDP/77971mSingapore
- UDP datagram flood, variant 751.79.209.109/32UDP/77771mSingapore
- UDP datagram flood, variant 751.79.163.179/32UDP/270151mSingapore
- UDP datagram flood, variant 7136.85.43.128/32UDP/533m 19sSingapore
- UDP datagram flood, variant 735.213.168.168/32UDP/533m 19sSingapore
- TCP connection flood103.170.217.245/32TCP/801mSingapore
- UDP datagram flood, variant 747.84.148.166/32UDP/200371mSingapore
- UDP datagram flood, variant 715.235.174.97/32UDP/77772mSingapore
- UDP datagram flood, variant 791.108.17.23/32UDP/3200330sSingapore
- TCP connection flood103.170.217.245/32TCP/801mSingapore
- TCP connection flood103.170.217.245/32TCP/801mSingapore
- UDP datagram flood, variant 1340.27.47.155/32UDP/301202mSingapore
- UDP datagram flood, variant 715.235.174.97/32UDP/77772mSingapore
- TCP connection flood159.223.55.94/32TCP/221mSingapore
- UDP datagram flood, variant 751.79.163.179/32UDP/270151mSingapore
- UDP datagram flood, variant 12136.85.43.128/32UDP/533m 19sSingapore
- UDP datagram flood, variant 751.79.163.179/32UDP/270151mSingapore
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- TCP connection flood15.235.174.103/32TCP/144001mSingapore
- UDP payload flood185.214.125.159/32UDP/4432m 29sSingapore
- TCP connection flood15.235.174.103/32TCP/144001mSingapore
- UDP datagram flood, variant 7209.25.142.22/32UDP/12111mSingapore
- UDP datagram flood, variant 735.213.168.168/32UDP/533m 19sSingapore
- UDP payload flood185.214.125.159/32UDP/4432m 29sSingapore
- TCP connection flood15.235.174.103/32TCP/144001mSingapore
- TCP connection flood47.84.67.250/32TCP/4431mSingapore
- TCP connection flood47.84.67.250/32TCP/4431mSingapore
- TCP connection flood47.84.67.250/32TCP/4431mSingapore
- UDP payload flood185.214.125.159/32UDP/4432m 29sSingapore
- TCP connection flood43.159.18.113/32TCP/143011mSingapore
- TCP connection flood43.159.18.115/32TCP/143011mSingapore
- TCP connection flood43.159.18.115/32TCP/143011mSingapore
botnet.cl reports infrastructure it observed. An address appearing here identifies a target or a relay, not a person responsible for the attack.