City: Amsterdam
Region: Noord Holland
Country: The Netherlands
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
| IP | Type | Details | Datetime |
|---|---|---|---|
| 45.148.10.247 | botsattack | 45.148.10.247/Trojan Linux |
2025-11-19 14:09:00 |
| 45.148.10.241 | attack | DDoS Inbound |
2023-11-15 18:54:04 |
| 45.148.10.28 | attackspam | Oct 13 20:18:40 sshgateway sshd\[2360\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.148.10.28 user=root Oct 13 20:18:43 sshgateway sshd\[2360\]: Failed password for root from 45.148.10.28 port 40178 ssh2 Oct 13 20:19:07 sshgateway sshd\[2364\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.148.10.28 user=root |
2020-10-14 02:28:44 |
| 45.148.10.15 | attackspambots | Bruteforce detected by fail2ban |
2020-10-13 21:25:53 |
| 45.148.10.186 | attackspam | Unable to negotiate with 45.148.10.186 port 47964: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth] |
2020-10-13 21:24:21 |
| 45.148.10.28 | attackbotsspam | SSH Server Abuse (45.148.10.28 as |
2020-10-13 17:43:00 |
| 45.148.10.15 | attackbotsspam | Oct 13 05:18:03 server2 sshd\[31409\]: Invalid user user from 45.148.10.15 Oct 13 05:18:48 server2 sshd\[31424\]: Invalid user server from 45.148.10.15 Oct 13 05:19:33 server2 sshd\[31465\]: Invalid user steam from 45.148.10.15 Oct 13 05:20:17 server2 sshd\[31678\]: Invalid user vmware from 45.148.10.15 Oct 13 05:21:00 server2 sshd\[31685\]: Invalid user microsoft from 45.148.10.15 Oct 13 05:21:44 server2 sshd\[31730\]: Invalid user cloud from 45.148.10.15 |
2020-10-13 12:52:46 |
| 45.148.10.186 | attackspam | Oct 13 05:33:03 ns308116 sshd[11001]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.148.10.186 user=root Oct 13 05:33:05 ns308116 sshd[11001]: Failed password for root from 45.148.10.186 port 41866 ssh2 Oct 13 05:33:38 ns308116 sshd[11016]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.148.10.186 user=root Oct 13 05:33:40 ns308116 sshd[11016]: Failed password for root from 45.148.10.186 port 39380 ssh2 Oct 13 05:34:15 ns308116 sshd[11027]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.148.10.186 user=root ... |
2020-10-13 12:50:57 |
| 45.148.10.15 | attack | Oct 12 23:36:06 srv-ubuntu-dev3 sshd[31523]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.148.10.15 Oct 12 23:36:06 srv-ubuntu-dev3 sshd[31523]: Invalid user user from 45.148.10.15 Oct 12 23:36:08 srv-ubuntu-dev3 sshd[31523]: Failed password for invalid user user from 45.148.10.15 port 40704 ssh2 Oct 12 23:36:38 srv-ubuntu-dev3 sshd[31590]: Invalid user 123Diego from 45.148.10.15 Oct 12 23:36:38 srv-ubuntu-dev3 sshd[31590]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.148.10.15 Oct 12 23:36:38 srv-ubuntu-dev3 sshd[31590]: Invalid user 123Diego from 45.148.10.15 Oct 12 23:36:40 srv-ubuntu-dev3 sshd[31590]: Failed password for invalid user 123Diego from 45.148.10.15 port 59760 ssh2 Oct 12 23:37:17 srv-ubuntu-dev3 sshd[31656]: Invalid user Alphanetworks from 45.148.10.15 Oct 12 23:37:17 srv-ubuntu-dev3 sshd[31656]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rh ... |
2020-10-13 05:40:39 |
| 45.148.10.186 | attack | Fail2Ban |
2020-10-13 05:39:02 |
| 45.148.10.15 | attackbotsspam | Fail2Ban |
2020-10-12 05:52:51 |
| 45.148.10.65 | attackbots | Invalid user ubuntu from 45.148.10.65 port 43138 |
2020-10-12 05:36:52 |
| 45.148.10.15 | attack | Brute force attempt |
2020-10-11 21:59:38 |
| 45.148.10.65 | attackspam | Oct 01 10:49:15 host sshd[12378]: Invalid user ubuntu from 45.148.10.65 port 41060 |
2020-10-11 21:43:21 |
| 45.148.10.28 | attack | Fail2Ban automatic report: SSH brute-force: |
2020-10-11 21:05:28 |
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
NetRange: 45.139.136.0 - 45.150.51.255
CIDR: 45.139.160.0/19, 45.148.0.0/15, 45.150.0.0/19, 45.150.32.0/20, 45.139.136.0/21, 45.150.48.0/22, 45.139.192.0/18, 45.139.144.0/20, 45.144.0.0/14, 45.140.0.0/14
NetName: RIPE
NetHandle: NET-45-139-136-0-1
Parent: NET45 (NET-45-0-0-0-0)
NetType: Early Registrations, Transferred to RIPE NCC
OriginAS:
Organization: RIPE Network Coordination Centre (RIPE)
RegDate: 2014-05-22
Updated: 2025-04-14
Comment: These addresses have been further assigned to users in the RIPE NCC region. Please note that the organization and point of contact details listed below are those of the RIPE NCC not the current address holder. ** You can find user contact information for the current address holder in the RIPE database at http://www.ripe.net/whois.
Ref: https://rdap.arin.net/registry/ip/45.139.136.0
ResourceLink: https://apps.db.ripe.net/db-web-ui/query
ResourceLink: whois.ripe.net
OrgName: RIPE Network Coordination Centre
OrgId: RIPE
Address: P.O. Box 10096
City: Amsterdam
StateProv:
PostalCode: 1001EB
Country: NL
RegDate:
Updated: 2013-07-29
Ref: https://rdap.arin.net/registry/entity/RIPE
ReferralServer: whois.ripe.net
ResourceLink: https://apps.db.ripe.net/db-web-ui/query
OrgAbuseHandle: ABUSE3850-ARIN
OrgAbuseName: Abuse Contact
OrgAbusePhone: +31205354444
OrgAbuseEmail: abuse@ripe.net
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE3850-ARIN
OrgTechHandle: RNO29-ARIN
OrgTechName: RIPE NCC Operations
OrgTechPhone: +31 20 535 4444
OrgTechEmail: hostmaster@ripe.net
OrgTechRef: https://rdap.arin.net/registry/entity/RNO29-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 45.148.10.49
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39117
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;45.148.10.49. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026081000 1800 900 604800 86400
;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Aug 10 17:30:45 CST 2026
;; MSG SIZE rcvd: 105Host 49.10.148.45.in-addr.arpa not found: 2(SERVFAIL);; Got SERVFAIL reply from 183.60.83.19, trying next server
Server: 183.60.82.98
Address: 183.60.82.98#53
** server can't find 49.10.148.45.in-addr.arpa: SERVFAIL
| IP | Type | Details | Datetime |
|---|---|---|---|
| 183.129.202.11 | attack | firewall-block, port(s): 1433/tcp |
2019-10-22 22:21:33 |
| 172.69.63.19 | attackspambots | Brute forcing admin username on wordpress login page |
2019-10-22 21:54:21 |
| 192.99.12.24 | attack | 2019-10-22T14:59:10.058594lon01.zurich-datacenter.net sshd\[14678\]: Invalid user admin from 192.99.12.24 port 37386 2019-10-22T14:59:10.065399lon01.zurich-datacenter.net sshd\[14678\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns506807.ip-192-99-12.net 2019-10-22T14:59:12.061720lon01.zurich-datacenter.net sshd\[14678\]: Failed password for invalid user admin from 192.99.12.24 port 37386 ssh2 2019-10-22T15:03:41.691489lon01.zurich-datacenter.net sshd\[14782\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns506807.ip-192-99-12.net user=root 2019-10-22T15:03:44.229588lon01.zurich-datacenter.net sshd\[14782\]: Failed password for root from 192.99.12.24 port 56980 ssh2 ... |
2019-10-22 22:33:09 |
| 118.89.221.36 | attackspam | Oct 22 13:32:55 apollo sshd\[23968\]: Failed password for root from 118.89.221.36 port 42447 ssh2Oct 22 13:45:44 apollo sshd\[23987\]: Failed password for root from 118.89.221.36 port 41934 ssh2Oct 22 13:50:46 apollo sshd\[24003\]: Failed password for root from 118.89.221.36 port 38760 ssh2 ... |
2019-10-22 22:11:59 |
| 93.188.2.5 | attackspambots | Automatic report - Banned IP Access |
2019-10-22 22:31:21 |
| 123.206.17.141 | attackbots | 2019-10-22T14:34:20.687221shield sshd\[31980\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.17.141 user=root 2019-10-22T14:34:23.561391shield sshd\[31980\]: Failed password for root from 123.206.17.141 port 32523 ssh2 2019-10-22T14:34:25.424694shield sshd\[31980\]: Failed password for root from 123.206.17.141 port 32523 ssh2 2019-10-22T14:34:31.646586shield sshd\[31980\]: Failed password for root from 123.206.17.141 port 32523 ssh2 2019-10-22T14:34:33.939801shield sshd\[31980\]: Failed password for root from 123.206.17.141 port 32523 ssh2 |
2019-10-22 22:37:54 |
| 159.203.201.8 | attack | 10/22/2019-13:50:52.684705 159.203.201.8 Protocol: 6 ET DROP Dshield Block Listed Source group 1 |
2019-10-22 22:08:50 |
| 115.150.59.53 | attackspambots | firewall-block, port(s): 23/tcp |
2019-10-22 22:28:55 |
| 108.61.187.208 | attackbotsspam | Oct 22 14:09:31 fv15 sshd[30138]: reveeclipse mapping checking getaddrinfo for 108.61.187.208.vultr.com [108.61.187.208] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 22 14:09:32 fv15 sshd[30138]: Failed password for invalid user lancui from 108.61.187.208 port 57422 ssh2 Oct 22 14:09:32 fv15 sshd[30138]: Received disconnect from 108.61.187.208: 11: Bye Bye [preauth] Oct 22 14:29:38 fv15 sshd[10801]: reveeclipse mapping checking getaddrinfo for 108.61.187.208.vultr.com [108.61.187.208] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 22 14:29:41 fv15 sshd[10801]: Failed password for invalid user pi from 108.61.187.208 port 36494 ssh2 Oct 22 14:29:41 fv15 sshd[10801]: Received disconnect from 108.61.187.208: 11: Bye Bye [preauth] Oct 22 14:34:19 fv15 sshd[504]: reveeclipse mapping checking getaddrinfo for 108.61.187.208.vultr.com [108.61.187.208] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 22 14:34:21 fv15 sshd[504]: Failed password for invalid user ui from 108.61.187.208 port 49574 ssh2 O........ ------------------------------- |
2019-10-22 22:14:42 |
| 23.129.64.214 | attack | Oct 22 14:26:35 vpn01 sshd[6068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.129.64.214 Oct 22 14:26:37 vpn01 sshd[6068]: Failed password for invalid user admin from 23.129.64.214 port 49811 ssh2 ... |
2019-10-22 22:11:07 |
| 222.186.173.180 | attackspambots | SSH scan :: |
2019-10-22 21:55:33 |
| 175.158.50.61 | attackspambots | Failed password for root from 175.158.50.61 port 53703 ssh2 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.158.50.61 user=root Failed password for root from 175.158.50.61 port 48733 ssh2 Invalid user team from 175.158.50.61 port 11708 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.158.50.61 |
2019-10-22 22:17:44 |
| 45.136.110.16 | attack | 10/22/2019-10:08:15.164224 45.136.110.16 Protocol: 6 ET SCAN NMAP -sS window 1024 |
2019-10-22 22:30:48 |
| 45.79.144.96 | attack | 2019-10-22 07:51:01,035 fail2ban.actions [1798]: NOTICE [sshd] Ban 45.79.144.96 |
2019-10-22 22:00:36 |
| 222.120.190.185 | attackspam | firewall-block, port(s): 5555/tcp |
2019-10-22 22:13:08 |