ABUSE.MOM
THREAT REPORT

IP Threat Report
45.141.233.210

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 14:00:48
First seen: 2026-02-24 22:00:06
Last seen: 2026-03-10 08:00:05
220

⛔ Verdict: BLOCK

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

UA_CHANGEDDANGER_PATHRATIO_404BURSTREFERERREDIRECT_PROBE
01

Geolocation & Classification

IP Address
45.141.233.210
Type
Residential
Country
🇬🇧 United Kingdom
City
London
ISP
MEVSPACE sp. z o.o.
Organization
Razinet
Autonomous System
AS201814 MEVSPACE sp. z o.o.
Hit Count
19
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 3Medium-risk: admin panels, config files+30
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Danger strong hits: 9High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 5Medium-risk: admin panels, config files+50
Burst: 9 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Σ = 545
03

Observed Activity

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

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

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

04

Timeline

2026-02-24 22:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Danger strong hits: 6 (+100), Danger medium hits: 3 (+30)
2026-03-10 08:00:05
Last malicious request observed
Total score reached: 220/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

MEVSPACE sp. z o.o.
AS201814 · 🇬🇧 United Kingdom
06

Recommendations

Actions taken & recommended

  • IP 45.141.233.210 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 45.141.233.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 45.141.233.210: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🔎 Path Enumeration Protection

Block scanning from 45.141.233.210: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Traffic Flood Defense

IP 45.141.233.210 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

07

Neighbors in 45.141.233.0/24

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

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (3)
PortServiceRiskDescription
135UnknownLowService on port 135
5357UnknownLowService on port 5357
5985UnknownLowService on port 5985

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

45.141.233.210 has been assigned a threat score of 220/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

User-Agent AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

Threat intelligence analysis has linked 45.141.233.210 to malicious activity originating from London, United Kingdom, operating on the network of MEVSPACE sp. z o.o.. The address has been under observation since its initial detection. The address has been active for 13 days in our monitoring system, producing 19 flagged requests at a rate of ~1.5/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. At 220/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

45.141.233.208 (210)45.141.233.207 (110)View all →

🏢 Same network: AS201814

146.19.24.209 (225)109.205.211.39 (220)45.141.233.208 (210)193.34.212.68 (190)194.180.49.38 (120)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Responsible Disclosure Ethics

Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.

🔍 Check Any IP Address

Share this report: