ABUSE.MOM
THREAT REPORT

IP Threat Report
185.220.101.30

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 06:21:31
First seen: 2026-05-22 08:00:19
Last seen: 2026-05-27 06:17:19
83

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHMETHODRATIO_404REFERER
01

Geolocation & Classification

IP Address
185.220.101.30
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
70
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 1Medium-risk: admin panels, config files+10
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
Σ = 83
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-22 08:00:19
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: 1 (+10), Foreign referer (+10)
2026-05-27 06:17:19
Last malicious request observed
Total score reached: 83/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

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

🤖 User-Agent Anomaly Defense

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

07

Neighbors in 185.220.101.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
dnsbl.dronebl.org
✓ Clean
bl.spamcop.net
✓ Clean
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net

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

10

Threat Analysis

185.220.101.30 has been assigned a threat score of 83/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

185.220.101.30 is registered in an unknown location. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 4-day observation window, we recorded 70 hostile requests from this IP — roughly 17.5 per day on average. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. At 83/100, this IP warrants immediate defensive action.

11

Related Threats

🇤🇤 Top threats from ??

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.

💡 Open Source Intelligence Methods

OSINT techniques leverage publicly available information for security research. DNS records, WHOIS data, certificate transparency logs, social media, and code repositories all provide valuable intelligence for threat analysis without requiring special access or tools.

🔍 Check Any IP Address

Share this report: