IP abuse report188.240.59.62

Critical Hosting / Datacenter IPv4 United Kingdom AS25369

188.240.59.62 is an IPv4 address located in London, United Kingdom. It belongs to a network operated by Hydra Communications Ltd (AS25369). The address is listed by 3 of the threat-intelligence sources we track and carries a confidence score of 100/100. It has also been reported 1 time(s) by the community.

Last updated Listing sources 3 Community Reports 1 How the score works
Provider notified This IP was reported to its network operator Hydra Communications Ltd · 2026-11-15 · IPDB-AR-007683 Awaiting reply Show detailsHide
  1. DetectedScore 100/100
  2. Notice sent2026-11-15 02:33
  3. Deliveredinfrawat.ch
  4. Operator response Waiting · 5 days ago

The IP-DB Abuse Desk sent an abuse notice with supporting evidence to Hydra Communications Ltd's registered abuse contact on 2026-11-15 02:33: abuse@infrawat.ch

This notice covers 4 address(es) on the same network. View public record · IPDB-AR-007683 →
Listing sources3
Community Reports1
Distinct Reporters1
Last seen 26 minutes ago

IP Information

ISP / Organization
Hydra Communications Ltd
ASN
AS25369 BANDWIDTH-AS
ASN Domain
zare.com
IP Range
188.240.59.0/26
Regional Registry
RIPENCC
Connection Type
Hosting / Datacenter
Country
United Kingdom (GB)
Region / State
England
City
LondonLocal database
City of LondonLive service

The two sources report different cities. Neither is confirmed; the country is the reliable part.

Time Zone
Europe/London
Abuse contact
abuse@infrawat.ch The abuse mailbox this network lists with its regional registry. Report traffic from this IP here, with logs and timestamps.

City is an estimate. The country is reliable; the city varies by provider.

Approximate location

City level
London England, United Kingdom
Coordinates
51.51, -0.09
Network
AS25369 Hydra Communications Ltd
Open on the threat map

The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.

Network Neighbourhood

188.240.59.0/24

53 of the 256 addresses in 188.240.59.0/24 are listed by our sources (20.7%).

Only a small part of the block is listed, which is more consistent with an isolated incident than with the network itself.

Examples from the same block
188.240.59.2188.240.59.3188.240.59.4188.240.59.7188.240.59.8188.240.59.10188.240.59.11188.240.59.12

An address is not guiltier for having a few listed neighbours, which is why this stays out of the confidence score entirely while the block is mostly clean. It contributes at most 20 points, and only once a substantial share of the block is listed — that ceiling is deliberate: neighbours alone can raise an address to "low" and no further.

Threat Evidence

Last 30 days: how many feeds listed this address each day, and the community reports filed.

Blocklist feeds Community reports

Blacklist Matches

3

In our pool since: 2026-08-28 11:17 (2 months ago) · Last confirmed: 2026-11-20 06:50

Attack Source 1
SourceScopeFirst seenConfirmed
IP-DB Sensor Network Single address 2026-11-03 10:48 2026-11-20 06:5026 minutes ago
Malicious Activity 1
SourceScopeFirst seenConfirmed
Binary Defense Banlist Single address 2026-11-20 03:17 2026-11-20 06:4729 minutes ago
SSH Brute Force 1
SourceScopeFirst seenConfirmed
James Brine Brute-Force Hosts Single address 2026-11-17 05:17 2026-11-20 06:4828 minutes ago

“Confirmed” is the moment the address was still on that source at its most recent fetch — the feeds are replaced wholesale on every refresh. Per-source “first seen” only began being recorded on 30 August 2026, so for listings older than that this column shows the start of record-keeping. The address-level history is the “in our pool since” value above.

IP-DB Sensor · free honeypot

Catch addresses like this on your own server

Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.

  • Realistic decoys for VPN gateways, mail, web panels and databases
  • Names exploit attempts by their CVE signature
  • One-command install; runs unprivileged and never touches your real services

While a Sensor reports, your daily API quota rises to 30,000 lookups.

root@web-01 — ipdb-sensor DEMO
● ipdb-sensor.serviceactive (running)
4hits
4decoys
1blocked
  1. 14:02:07 ssh:22 188.240.59.62 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 188.240.59.62 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 188.240.59.62 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 188.240.59.62 Citrix Bleed scan CVE-2023-4966
  5. 14:02:20 ✓ evidence logged → added to your blocklist
Sample output — if this address probed your server

Community Reports 1

Report This IP

Who reported this address, when, and on what grounds.

0Last 24 Hours
0Last 7 Days
1Last 30 Days
1Last 90 Days
  1. nak Registered member
    8 days ago 2026-11-11 10:22Reported from: Japan (JP)
    Reason: Vulnerability Scanning
    Observed by PHP honeypot (static responder; no code executed). 2 requests between 2026-11-08 02:11 and 2026-11-11 07:01 UTC, on 2 distinct days. Automated MCP/SSE endpoint scanner. Attack attempts: - MCP and SSE endpoint probing [2 requests]: GET /api/mcp, /sse -> discovers exposed AI model context protocol endpoints Signatures: ai-triage

Reporters' IP addresses are never published — only the country they reported from.

Listing History

1
Added to the pool
2 months ago · score at the time: 86/100 · carried by 2 sources
2026-08-28 11:17

The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.

Frequently asked questions about 188.240.59.62

Is 188.240.59.62 safe?

No. 188.240.59.62 scores 100/100 with strong, recent evidence of abuse (3 sources, 1 community report). Blocking it at your firewall is advisable.

Who owns 188.240.59.62?

188.240.59.62 is announced by AS25369 and operated by Hydra Communications Ltd. It sits in the 188.240.59.0/26 block registered with RIPENCC.

Where is 188.240.59.62 located?

Geolocation places 188.240.59.62 in London, United Kingdom. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 188.240.59.62 on a blacklist?

Yes. 188.240.59.62 is currently listed by 3 threat sources: Binary Defense Banlist, James Brine Brute-Force Hosts, IP-DB Sensor Network.

How do I report abuse from 188.240.59.62?

Send your log lines to the network's abuse contact, abuse@infrawat.ch, and file a report on IP-DB so others can see it too.

Run this check via the API

The same score and evidence are available as JSON, free with an API key.

API documentation →
curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/188.240.59.62

Guides for this IP