ABUSE.MOM
THREAT REPORT

IP Threat Report
72.56.155.24

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-08 13:37:20
First seen: 2026-08-17 00:48:57
Last seen: 2026-08-23 02:01:17
230

⛔ Verdict: BLOCK

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

BURSTDANGER_PATH
01

Geolocation & Classification

IP Address
72.56.155.24
Type
Hosting
Country
🇷🇺 Russia
City
Moscow
ISP
Lease
Organization
Unknown
Autonomous System
AS209641 IHOR HOSTING LTD
Hit Count
174
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 200/10sAbnormally fast request rate — automated scanning+35
Burst 200/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 46Medium-risk: admin panels, config files+60
Danger strong hits: 307High-risk paths: shells, RCE vectors, exploits+100
Σ = 230
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-08-17 00:48:57
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 200/10s (+35), Burst 200/2s (+35), Danger medium hits: 46 (+60)
2026-08-23 02:01:17
Last malicious request observed
Total score reached: 230/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Lease
AS209641 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 72.56.155.24.

07

Neighbors in 72.56.155.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
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

72.56.155.24 has been assigned a threat score of 230/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 72.56.155.24, geolocated to Moscow, Russia, operating on the network of Lease, as a source of suspicious network activity. Over a period of 6 days, this IP generated 174 malicious requests, averaging approximately 29 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 114 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. At 230/100, this is an extremely high-risk address. All traffic should be considered hostile.

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 Russia

157.22.102.172 (313)178.130.54.159 (288)213.183.54.30 (275)185.103.167.63 (265)72.56.191.6 (265)View all →

🏢 Same network: AS209641

72.56.154.249 (255)72.56.152.194 (255)72.56.146.67 (255)72.56.154.220 (255)72.56.154.222 (230)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Submarine Cable and Internet Exchange Points

Internet traffic routing through a limited number of submarine cables and exchange points creates natural chokepoints. Understanding these routing patterns helps explain geographic clustering of certain attack types and latency-based scanning behaviors.

🔍 Check Any IP Address

Share this report: