BNETv2 · Vector 2
BNETv2: TCP connection and payload flood
Opens multiple nonblocking TCP connections and repeatedly writes configured or random payload bytes while replacing failed connections. No built-in HTTP or TLS request construction is established.
57 observations · Last 30 days · Latest observation
Most affected countries
Last 30 days
Most affected networks
- Infraly, LLCAS40052928
- 1 of 1 Servers CorpAS2062867
- OVH SASAS162765
- VibeGAMES B.V.AS489253
- Akamai Connected CloudAS639492
- Ecxon Datacenter LTDAAS2707642
- Datacamp LimitedAS600682
- Pine Hosting LTDAS1989901
Last 30 days
Recent observations
- TCP connection and payload flood185.244.106.66/32TCP/301202mUnited States
- TCP connection and payload flood185.244.106.66/32TCP/301202mUnited States
- TCP connection and payload flood185.244.106.66/32TCP/301202mUnited States
- TCP connection and payload flood185.244.106.66/32TCP/301202mUnited States
- TCP connection and payload flood185.244.106.66/32TCP/301202mUnited States
- TCP connection and payload flood185.244.106.66/32TCP/301202mUnited States
- TCP connection and payload flood185.244.106.7/32TCP/301203m 20sUnited States
- TCP connection and payload flood185.29.166.41/32TCP/255651mNetherlands
- TCP connection and payload flood185.29.166.41/32TCP/255651mNetherlands
- TCP connection and payload flood185.244.106.7/32TCP/301202mUnited States
- TCP connection and payload flood89.213.214.165/32TCP/301203m 20sUnited States
- TCP connection and payload flood91.190.154.74/32TCP/301202mUnited States
- TCP connection and payload flood172.105.93.187/32TCP/270151m 30sGermany
- TCP connection and payload flood172.105.93.187/32TCP/270153m 20sGermany
- TCP connection and payload flood158.69.212.62/32TCP/11942mCanada
- TCP connection and payload flood54.37.117.0/32TCP/222mFrance
- TCP connection and payload flood54.37.117.233/32TCP/222mFrance
- TCP connection and payload flood54.37.117.233/32TCP/222mFrance
- TCP connection and payload flood54.37.117.233/32TCP/222mFrance
- TCP connection and payload flood104.234.119.157/32TCP/301202mBrazil
- TCP connection and payload flood104.234.119.157/32TCP/301202mBrazil
- TCP connection and payload flood91.190.154.74/32TCP/301202mUnited States
- TCP connection and payload flood91.190.154.74/32TCP/301202mUnited States
- TCP connection and payload flood91.190.154.74/32TCP/301201mUnited States
- TCP connection and payload flood91.190.154.74/32TCP/301202mUnited States
- TCP connection and payload flood91.190.154.74/32TCP/301202mUnited States
- TCP connection and payload flood91.190.154.74/32TCP/301202mUnited States
- TCP connection and payload flood91.190.154.74/32TCP/301202mUnited States
- TCP connection and payload flood45.141.24.195/32TCP/301202mUnited States
- TCP connection and payload flood45.141.24.195/32TCP/301202mUnited States
- TCP connection and payload flood45.141.24.195/32TCP/301202mUnited States
- TCP connection and payload flood91.190.154.74/32TCP/301202mUnited States
- TCP connection and payload flood91.190.154.74/32TCP/301202mUnited States
- TCP connection and payload flood185.244.106.12/32TCP/301202mUnited States
- TCP connection and payload flood212.189.58.50/32TCP/301201mUnited States
- TCP connection and payload flood170.205.24.84/32TCP/301201mUnited States
- TCP connection and payload flood45.141.24.195/32TCP/301201mUnited States
- TCP connection and payload flood45.141.24.195/32TCP/301201mUnited States
- TCP connection and payload flood185.244.106.12/32TCP/301202mUnited States
- TCP connection and payload flood185.244.106.12/32TCP/301202mUnited States
botnet.cl reports infrastructure it observed. An address appearing here identifies a target or a relay, not a person responsible for the attack.