All families · Country
Attacks observed in Singapore
All families attack observations affecting networks in Singapore: targeted prefixes, affected operators, attack methods, and timing over the last 30 days.
195 observations · Last 30 days · Latest observation
Most affected networks
- OVH SASAS1627631
- ACEAS13934125
- Telegram Messenger IncAS6201424
- VibeGAMES B.V.AS4892514
- Alibaba Cloud (Singapore) Private LimitedAS13496313
- SlashN Services Pte. Ltd.AS20895911
- Tencent Building, Kejizhongyi AvenueAS1322039
- Akamai Connected CloudAS639499
Last 30 days
Most observed methods
- Potassium: UDP datagram flood, variant 774
- Cereal2: UDP flood with large datagrams (default 1400-byte payload)28
- Potassium: TCP connection flood24
- Cereal2: Raw IPv4/TCP packet flood variant 213
- Potassium: UDP payload flood12
- Cereal2: TCP connection and session-pool flood variant 19
- Cereal2: UDP flood with minimal datagrams (default 1-byte payload)7
- Cereal2: Raw IPv4/TCP packet flood variant 37
Last 30 days
Recent observations
- Potassium: UDP datagram flood, variant 751.79.163.179/32UDP/270151mSingapore
- Potassium: UDP datagram flood, variant 7136.85.43.128/32UDP/533m 19sSingapore
- Potassium: UDP datagram flood, variant 735.213.168.168/32UDP/533m 19sSingapore
- Potassium: TCP connection flood103.170.217.245/32TCP/801mSingapore
- Potassium: UDP datagram flood, variant 747.84.148.166/32UDP/200371mSingapore
- Potassium: UDP datagram flood, variant 715.235.174.97/32UDP/77772mSingapore
- Potassium: UDP datagram flood, variant 791.108.17.23/32UDP/3200330sSingapore
- Potassium: TCP connection flood103.170.217.245/32TCP/801mSingapore
- Potassium: TCP connection flood103.170.217.245/32TCP/801mSingapore
- Potassium: UDP datagram flood, variant 1340.27.47.155/32UDP/301202mSingapore
- Potassium: UDP datagram flood, variant 715.235.174.97/32UDP/77772mSingapore
- Potassium: TCP connection flood159.223.55.94/32TCP/221mSingapore
- Cereal2: UDP flood with large datagrams (default 1400-byte payload)161.120.182.121/32UDP/801mSingapore
- Potassium: UDP datagram flood, variant 751.79.163.179/32UDP/270151mSingapore
- Potassium: UDP datagram flood, variant 12136.85.43.128/32UDP/533m 19sSingapore
- Potassium: UDP datagram flood, variant 751.79.163.179/32UDP/270151mSingapore
- Potassium: UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- Potassium: UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- Potassium: UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- Potassium: UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- Potassium: UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- Potassium: UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- Potassium: UDP datagram flood, variant 731.58.143.58/32UDP/77771mSingapore
- Potassium: TCP connection flood15.235.174.103/32TCP/144001mSingapore
- Potassium: UDP payload flood185.214.125.159/32UDP/4432m 29sSingapore
- Potassium: TCP connection flood15.235.174.103/32TCP/144001mSingapore
- Potassium: UDP datagram flood, variant 7209.25.142.22/32UDP/12111mSingapore
- Potassium: UDP datagram flood, variant 735.213.168.168/32UDP/533m 19sSingapore
- Potassium: UDP payload flood185.214.125.159/32UDP/4432m 29sSingapore
- Potassium: TCP connection flood15.235.174.103/32TCP/144001mSingapore
- Potassium: TCP connection flood47.84.67.250/32TCP/4431mSingapore
- Potassium: TCP connection flood47.84.67.250/32TCP/4431mSingapore
- Potassium: TCP connection flood47.84.67.250/32TCP/4431mSingapore
- Potassium: UDP payload flood185.214.125.159/32UDP/4432m 29sSingapore
- Potassium: TCP connection flood43.159.18.113/32TCP/143011mSingapore
- Potassium: TCP connection flood43.159.18.115/32TCP/143011mSingapore
- Potassium: TCP connection flood43.159.18.115/32TCP/143011mSingapore
- Potassium: TCP connection flood43.159.18.115/32TCP/143011mSingapore
- Potassium: UDP datagram flood, variant 756.10.64.91/32UDP/778830sSingapore
- Potassium: TCP connection flood43.159.18.112/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.