IP abuse report188.240.59.62
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.
Provider notified This IP was reported to its network operator Hydra Communications Ltd · 2026-11-15 · IPDB-AR-007683 Awaiting reply Show detailsHide
- DetectedScore 100/100
- Notice sent2026-11-15 02:33
- Deliveredinfrawat.ch
- 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
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 databaseCity 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- Coordinates
- 51.51, -0.09
- Network
- AS25369 Hydra Communications Ltd
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/2453 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.
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.
What this address is listed for: feed categories count sources, community categories count reports.
Where community reports were filed from. Only the reporter's country is shown, never their address.
Top reporter countries
- Japan1
When each feed first and last carried this address, over the last 30 days.
Blacklist Matches
3In our pool since: 2026-08-28 11:17 (2 months ago) · Last confirmed: 2026-11-20 06:50
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| IP-DB Sensor Network | Single address | 2026-11-03 10:48 | 2026-11-20 06:5026 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Binary Defense Banlist | Single address | 2026-11-20 03:17 | 2026-11-20 06:4729 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| 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.
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.
- 14:02:07 ssh:22 188.240.59.62 login attempt root / ••••••
- 14:02:10 globalprotect:443 188.240.59.62 exploit attempt CVE-2024-3400
- 14:02:13 owa:4443 188.240.59.62 password spray Exchange OWA
- 14:02:16 netscaler:8443 188.240.59.62 Citrix Bleed scan CVE-2023-4966
- 14:02:20 ✓ evidence logged → added to your blocklist
Community Reports 1
Report This IPWho reported this address, when, and on what grounds.
-
nak Registered memberReason: 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
1The 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