ABUSE.MOM
THREAT REPORT

IP Threat Report
72.56.153.129

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 06:17:25
First seen: 2026-02-17 17:25:05
Last seen: 2026-02-17 17:26:16
105

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERERIMPORT
01

Geolocation & Classification

IP Address
72.56.153.129
Type
Residential
Country
🇷🇺 Russia
City
Moscow
ISP
R Fixed Center
Organization
Unknown
Autonomous System
AS209372 WS Telecom Inc
Hit Count
3
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 6Medium-risk: admin panels, config files+60
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
Σ = 105
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-02-17 17:25:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 6 (+60), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-02-17 17:26:16
Last malicious request observed
Total score reached: 105/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

R Fixed Center
AS209372 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

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

07

Neighbors in 72.56.153.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.

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

72.56.153.129 has been assigned a threat score of 105/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:

Path Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 72.56.153.129 to malicious activity originating from Moscow, Russia, operating on the network of R Fixed Center. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 3 malicious requests, averaging approximately 3 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 100 malicious IPs originating from Russia, positioning it as a notable contributor to global threat activity. At 105/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 Russia

72.56.159.192 (215)72.56.153.125 (215)72.56.191.123 (215)72.56.152.23 (180)72.56.188.137 (180)View all →

🏢 Same network: AS209372

72.56.159.192 (215)72.56.153.125 (215)72.56.191.123 (215)72.56.152.23 (180)72.56.188.137 (180)View all →
12

Security Intelligence

💡 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.

💡 WebSocket Security Considerations

WebSocket connections bypass traditional HTTP security controls, creating opportunities for cross-site WebSocket hijacking, denial of service, and data injection. Proper origin validation, authentication, and message rate limiting are essential for secure WebSocket implementations.

🔍 Check Any IP Address

Share this report: