ABUSE.MOM
THREAT REPORT

IP Threat Report
34.73.122.75

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 18:30:40
First seen: 2026-04-06 14:00:07
Last seen: 2026-04-06 16:00:05
180

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404
01

Geolocation & Classification

IP Address
34.73.122.75
Type
Hosting
Country
🇺🇸 United States
City
North Charleston
ISP
Google LLC
Organization
Google Cloud (us-east1)
Autonomous System
AS396982 Google LLC
Hit Count
4
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 19Medium-risk: admin panels, config files+60
Burst: 15 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 21 req / 10sAbnormally fast request rate — automated scanning+35
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 18 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 20 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 250
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-04-06 14:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 1 (+25), Danger medium hits: 19 (+60), Burst: 15 req / 2s (+35)
2026-04-06 16:00:05
Last malicious request observed
Total score reached: 180/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 34.73.122.75 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 34.73.122.0/24
  • 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 34.73.122.75.

🔎 Path Enumeration Protection

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

07

Neighbors in 34.73.122.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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

34.73.122.75 has been assigned a threat score of 180/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Request FloodingPath Enumeration

📊 Threat Analysis

34.73.122.75 is registered in North Charleston, United States, operating on the network of Google LLC. 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 4 flagged requests at a rate of ~4/day. 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 Request Flooding combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. With 143 flagged addresses, United States represents a significant presence in our threat database. At 180/100, this is an extremely high-risk address. All traffic should be considered hostile.

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.22.208.175 (285)34.166.187.0 (285)34.128.70.180 (285)View all →
12

Security Intelligence

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

💡 Honeypot Network Intelligence

Honeypots are decoy systems designed to attract and study attackers. Networks of honeypots provide early warning of new attack campaigns, reveal attacker tools and techniques, and generate high-confidence threat intelligence with minimal false positives.

🔍 Check Any IP Address

Share this report: