ABUSE.MOM
THREAT REPORT

IP Threat Report
5.255.123.158

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 10:11:40
First seen: 2026-05-27 01:55:12
Last seen: 2026-05-27 10:05:24
73

⛔ Verdict: BLOCK

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

BOT_UAMETHODRATIO_404REFERER
01

Geolocation & Classification

IP Address
5.255.123.158
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
12
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Σ = 73
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-05-27 01:55:12
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Foreign referer (+10), POST seen (+8)
2026-05-27 10:05:24
Last malicious request observed
Total score reached: 73/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 5.255.123.158 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 5.255.123.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

IP 5.255.123.158 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 User-Agent Anomaly Defense

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

07

Neighbors in 5.255.123.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
psbl.surriel.com

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

10

Threat Analysis

5.255.123.158 has been assigned a threat score of 73/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 5.255.123.158 to malicious activity originating from an unknown location. The address has been under observation since its initial detection. During its 1-day observation window, we recorded 12 hostile requests from this IP — roughly 12 per day on average. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. At 73/100, this IP warrants immediate defensive action.

11

Related Threats

🇤🇤 Top threats from ??

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.

💡 File Upload Vulnerabilities

Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.

🔍 Check Any IP Address

Share this report: