ABUSE.MOM
THREAT REPORT

IP Threat Report
3.91.86.227

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 19:12:48
First seen: 2026-03-25 00:00:09
Last seen: 2026-03-25 17:00:06
145

⛔ Verdict: BLOCK

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

BOT_UAUA_CHANGEDBURSTREFERER
01

Geolocation & Classification

IP Address
3.91.86.227
Type
Hosting
Country
🇺🇸 United States
City
Ashburn
ISP
Amazon Technologies Inc.
Organization
AWS EC2 (us-east-1)
Autonomous System
AS14618 Amazon.com, Inc.
Hit Count
4
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Burst: 11 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 11 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 145
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-03-25 00:00:09
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: Go-http-client (+40), UA changed for same IP (+25), Burst: 11 req / 2s (+35)
2026-03-25 17:00:06
Last malicious request observed
Total score reached: 145/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon Technologies Inc.
AS14618 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🤖 Bot Detection

Address UA spoofing from 3.91.86.227: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🌊 Flood / DDoS Mitigation

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

09

Blacklist Status (DNSBL)

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

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

3.91.86.227 has been assigned a threat score of 145/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 3.91.86.227, geolocated to Ashburn, United States, operating on the network of Amazon Technologies Inc., as a source of suspicious network activity. During its 1-day observation window, we recorded 4 hostile requests from this IP — roughly 4 per day on average. 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. The dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 201 blocked IPs in our database, making it a significant source of malicious traffic. A score of 145/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS14618

185.117.225.111 (275)185.117.225.174 (275)3.238.226.143 (263)3.237.21.73 (263)3.231.166.236 (263)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.

💡 Hacktivism and Ideological Attacks

Hacktivism combines hacking skills with political or social motivations. DDoS campaigns, website defacements, and data leaks target organizations based on ideological disagreements, adding unpredictable threat actors to the landscape.

🔍 Check Any IP Address

Share this report: