ABUSE.MOM
THREAT REPORT

IP Threat Report
185.220.101.9

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 09:02:10
First seen: 2026-03-22 20:52:57
Last seen: 2026-05-27 08:38:22
65

⛔ Verdict: BLOCK

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

BOT_UAFORM_SPAMMETHODRATIO_404REFERER
01

Geolocation & Classification

IP Address
185.220.101.9
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
151
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Foreign refererReferer from unrelated external domain+10
Form spam: latin_nameSpam/malware keywords in request content+0
Form spam: too_fastSpam/malware keywords in request content+0
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-03-22 20:52:57
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), Form spam: latin_name
2026-05-27 08:38:22
Last malicious request observed
Total score reached: 65/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 185.220.101.9 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

🔎 Path Enumeration Protection

Block scanning from 185.220.101.9: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

📧 Spam Protection

Enable CAPTCHA on all public forms. Add honeypot fields. Rate-limit submissions to 3 per minute per IP. Deploy Akismet or CleanTalk.

🤖 User-Agent Anomaly Defense

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

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

10

Threat Analysis

185.220.101.9 has been assigned a threat score of 65/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 185.220.101.9 to malicious activity originating from an unknown location. The address has been under observation since its initial detection. The address has been active for 65 days in our monitoring system, producing 151 flagged requests at a rate of ~2.3/day. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. At 65/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

11

Related Threats

🇤🇤 Top threats from ??

View all →
12

Security Intelligence

💡 SQL Injection Campaigns

SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

🔍 Check Any IP Address

Share this report: