ABUSE.MOM
THREAT REPORT

IP Threat Report
104.198.47.91

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 23:03:20
First seen: 2026-05-23 07:07:48
Last seen: 2026-05-24 09:59:42
105

⛔ Verdict: BLOCK

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

BURSTREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
104.198.47.91
Type
Hosting
Country
🇺🇸 United States
City
Council Bluffs
ISP
Google LLC
Organization
Google Cloud (us-central1)
Autonomous System
AS396982 Google LLC
Hit Count
81
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 129/10sAbnormally fast request rate — automated scanning+35
Burst 98/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 105
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-05-23 07:07:48
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 129/10s (+35), Burst 98/2s (+35), Foreign referer (+10)
2026-05-24 09:59:42
Last malicious request observed
Total score reached: 105/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

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

🤖 Bot Detection

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

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

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

10

Threat Analysis

104.198.47.91 has been assigned a threat score of 105/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:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 104.198.47.91 to malicious activity originating from Council Bluffs, United States, operating on the network of Google LLC. The address has been under observation since its initial detection. During its 1-day observation window, we recorded 81 hostile requests from this IP — roughly 81 per day on average. 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. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 140 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 105/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: AS396982

34.187.158.4 (340)34.186.187.208 (340)34.136.84.236 (288)35.254.215.135 (288)35.243.110.60 (288)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Critical Infrastructure Targeting

Attacks on power grids, water systems, and transportation networks have moved from theoretical to practical threats. Industrial control systems often lack modern security features, making them vulnerable to both targeted and opportunistic attacks.

🔍 Check Any IP Address

Share this report: