ABUSE.MOM
THREAT REPORT

IP Threat Report
135.136.20.14

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-06 05:17:29
First seen: 2026-09-05 11:08:11
Last seen: 2026-09-13 01:12:00
65

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 65/100. Total malicious requests observed: 273.

DANGER_PATHREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
135.136.20.14
Type
Hosting
Country
🇬🇧 United Kingdom
City
Manchester
ISP
M247 Europe SRL
Organization
M247 LTD
Autonomous System
AS9009 M247 Europe SRL
Hit Count
273
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger medium hits: 3Medium-risk: admin panels, config files+30
Foreign refererReferer from unrelated external domain+10
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 95
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-09-05 11:08:11
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 1 (+10), Danger medium hits: 2 (+20), Danger medium hits: 3 (+30)
2026-09-13 01:12:00
Last malicious request observed
Total score reached: 65/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

M247 Europe SRL
AS9009 · 🇬🇧 United Kingdom
06

Recommendations

Actions taken & recommended

  • IP 135.136.20.14 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 135.136.20.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 User-Agent Anomaly Defense

IP 135.136.20.14 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

07

Neighbors in 135.136.20.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

135.136.20.14 has been assigned a threat score of 65/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

Network traffic from 135.136.20.14, located in Manchester, United Kingdom, operating on the network of M247 Europe SRL, has been classified as malicious by our automated threat scoring engine. During its 7-day observation window, we recorded 273 hostile requests from this IP — roughly 39 per day on average. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Detected suspicious User-Agent anomalies including empty, forged, or rapidly rotating UA strings — characteristic of automated scanning tools. With 123 flagged addresses, United Kingdom represents a significant presence in our threat database. The score of 65/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇬🇧 Top threats from United Kingdom

45.86.203.126 (350)104.28.240.60 (340)104.28.192.67 (340)104.28.208.60 (340)194.32.120.30 (320)View all →

🏢 Same network: AS9009

45.91.20.151 (305)158.173.36.134 (305)135.136.42.150 (305)170.62.245.48 (305)45.91.20.141 (295)View all →
12

Security Intelligence

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 GeoIP Blocking Considerations

Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.

🔍 Check Any IP Address

Share this report: