Malicious IP Address Feed
Newly reported malicious IP addresses; 89,329 tracked.
24 indicators match · newest first · updated 2026-10-12 10:35 UTC
| First seen | Indicator | Category | Family | Reported by | Where | Network | Copy |
|---|---|---|---|---|---|---|---|
| 10-12 09:30 | 180.241.240[.]23 | Attacker | — | 1 feed | |||
| 10-12 09:30 | 180.241.241[.]8 | Attacker | — | 1 feed | |||
| 10-12 09:30 | 36.75.4[.]115 | Attacker | — | 1 feed | |||
| 10-12 08:55 | 180.241.242[.]3 | Attacker | — | 1 feed | |||
| 10-12 08:55 | 180.241.243[.]110 | Attacker | — | 1 feed | |||
| 10-12 08:55 | 180.244.0[.]79 | Attacker | — | 1 feed | |||
| 10-12 08:55 | 36.90.149[.]144 | Attacker | — | 1 feed | |||
| 10-12 08:20 | 36.73.143[.]0 | Attacker | — | 1 feed | |||
| 10-12 08:20 | 36.78.8[.]22 | Attacker | — | 1 feed | |||
| 10-12 07:50 | 2001[:]448a[:]5040[:]cdf3[:]6cf2[:]8fce[:]2a10[:]71ba | Attacker | — | 1 feed | |||
| 10-12 07:15 | 36.80.164[.]180 | Attacker | — | 1 feed | |||
| 10-12 06:41 | 36.80.163[.]201 | Attacker | — | 1 feed | |||
| 10-12 06:10 | 36.83.50[.]30 | Attacker | — | 1 feed | |||
| 10-12 05:55 | 180.243.200[.]68 | Attacker | — | 2 feeds | |||
| 10-12 04:35 | 36.64.148[.]186 | Attacker | — | 3 feeds | |||
| 10-12 04:35 | 125.162.214[.]119 | Attacker | — | 2 feeds | |||
| 10-12 04:35 | 125.165.111[.]72 | Attacker | — | 2 feeds | |||
| 10-12 04:35 | 110.137.131[.]55 | Attacker | — | 2 feeds | |||
| 10-12 04:35 | 180.241.36[.]150 | Attacker | — | 2 feeds | |||
| 10-12 04:35 | 180.241.39[.]87 | Attacker | — | 2 feeds | |||
| 10-12 04:35 | 180.246.205[.]2 | Attacker | — | 2 feeds | |||
| 10-12 04:35 | 36.75.103[.]103 | Attacker | — | 2 feeds | |||
| 10-12 04:35 | 36.75.103[.]192 | Attacker | — | 2 feeds | |||
| 10-12 04:35 | 180.252.174[.]196 | Attacker | — | 2 feeds |
Values are defanged (hxxp, [.]) so nothing here is a live link to malicious infrastructure. URL query strings are removed to protect victims. Copy copies the defanged form.