ABUSE.MOM
THREAT REPORT

IP Threat Report
72.56.154.3

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 14:29:10
First seen: 2026-08-12 10:20:22
Last seen: 2026-08-16 01:00:26
65

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 2Medium-risk: admin panels, config files+20
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 65
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-08-12 10:20:22
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 2 (+20), Foreign referer (+10)
2026-08-16 01:00:26
Last malicious request observed
Total score reached: 65/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Lease
AS209641 · 🇷🇺 Russia

We have detected 134 malicious IPs from this autonomous system.

View all IPs from AS209641 →
06

Recommendations

Actions taken & recommended

  • IP 72.56.154.3 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.154.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.154.3 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

07

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

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

10

Threat Analysis

72.56.154.3 has been assigned a threat score of 65/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

IP address 72.56.154.3 has been traced to Moscow, Russia, operating on the network of Lease. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 3-day observation window, we recorded 145 hostile requests from this IP — roughly 48.3 per day on average. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 2,652 malicious IPs originating from Russia, positioning it as a major contributor to global threat activity. At 65/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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.50.25.14 (273)185.103.167.63 (265)View all →

🏢 Same network: AS209641

72.56.154.249 (255)72.56.152.194 (255)72.56.147.97 (255)72.56.146.67 (255)72.56.154.220 (255)View all →
12

Security Intelligence

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 Web Cache Poisoning Attacks

Cache poisoning manipulates web cache behavior to serve malicious content to other users. By identifying unkeyed inputs that influence cached responses, attackers can inject JavaScript, redirect users, or cause denial of service at scale through the cache infrastructure.

🔍 Check Any IP Address

Share this report: