ABUSE.MOM
THREAT REPORT

IP Threat Report
217.154.5.232

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-31 21:07:18
First seen: 2026-07-04 22:11:25
Last seen: 2026-07-05 00:17:06
75

⛔ Verdict: BLOCK

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

BOT_UAREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
217.154.5.232
Type
Hosting
Country
🇫🇷 France
City
Paris
ISP
MISTRAL
Organization
Unknown
Autonomous System
AS8560 IONOS SE
Hit Count
3
02

Detection Signatures

SignatureDescriptionPointsSeverity
Foreign refererReferer from unrelated external domain+10
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 75
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-07-04 22:11:25
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Foreign referer (+10), UA bot: Go-http-client (+40), UA changed (+25)
2026-07-05 00:17:06
Last malicious request observed
Total score reached: 75/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

MISTRAL
AS8560 · 🇫🇷 France
06

Recommendations

Actions taken & recommended

  • IP 217.154.5.232 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 User-Agent Anomaly Defense

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

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
psbl.surriel.com
✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

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

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

217.154.5.232 is registered in Paris, France, operating on the network of MISTRAL. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 1 days in our monitoring system, producing 3 flagged requests at a rate of ~3/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Detected suspicious User-Agent anomalies including empty, forged, or rapidly rotating UA strings — characteristic of automated scanning tools. At 75/100, this IP warrants immediate defensive action.

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 France

217.154.3.67 (65)View all →

🏢 Same network: AS8560

109.228.60.189 (255)87.106.126.193 (255)217.160.67.220 (213)217.160.136.123 (190)74.208.55.148 (160)View all →
12

Security Intelligence

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

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