ABUSE.MOM
THREAT REPORT

IP Threat Report
193.202.9.154

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 10:06:05
First seen: 2026-04-18 19:00:05
Last seen: 2026-04-18 19:00:05
233

⛔ Verdict: BLOCK

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

BOT_UAUA_CHANGEDDANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
193.202.9.154
Type
Residential
Country
🇬🇧 United Kingdom
City
Islington
ISP
Alex Largman
Organization
Apex Data Solutions LLC
Autonomous System
AS59651 AS QualityNetwork
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: wgetKnown bot/crawler User-Agent detected+40
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 9High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 6Medium-risk: admin panels, config files+60
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 233
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-04-18 19:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: wget (+40), UA changed for same IP (+25), Danger strong hits: 9 (+100)
2026-04-18 19:00:05
Last malicious request observed
Total score reached: 233/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Alex Largman
AS59651 · 🇬🇧 United Kingdom
06

Recommendations

Actions taken & recommended

  • IP 193.202.9.154 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 193.202.9.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

Address UA spoofing from 193.202.9.154: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 193.202.9.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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

193.202.9.154 has been assigned a threat score of 233/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 193.202.9.154 to malicious activity originating from Islington, United Kingdom, operating on the network of Alex Largman. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. Our records show 112 malicious IPs originating from United Kingdom, positioning it as a significant contributor to global threat activity. At 233/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇬🇧 Top threats from United Kingdom

104.28.240.60 (340)104.28.208.60 (340)91.230.225.3 (305)45.86.203.224 (305)45.86.203.35 (305)View all →

🏢 Same network: AS59651

5.181.169.192 (313)170.168.175.156 (313)170.168.96.250 (313)170.168.175.34 (313)122.8.95.61 (268)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

🔍 Check Any IP Address

Share this report: