ABUSE.MOM
THREAT REPORT

IP Threat Report
129.153.76.167

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:09:11
First seen: 2026-03-12 09:00:04
Last seen: 2026-03-18 00:00:07
175

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
129.153.76.167
Type
Hosting
Country
🇺🇸 United States
City
Phoenix
ISP
Oracle Corporation
Organization
Oracle Cloud Infrastructure (us-phoenix-1)
Autonomous System
AS31898 Oracle Corporation
Hit Count
28
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: pythonKnown bot/crawler User-Agent detected+40
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 24High-risk paths: shells, RCE vectors, exploits+100
Σ = 425
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-12 09:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: python (+40), Danger strong hits: 2 (+50), 404 ratio 40-60% (+15)
2026-03-18 00:00:07
Last malicious request observed
Total score reached: 175/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Oracle Corporation
AS31898 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 129.153.76.167 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 129.153.76.167 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🔎 Path Enumeration Protection

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

09

Blacklist Status (DNSBL)

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

✓ Clean
Spamhaus ZEN

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

10

Threat Analysis

129.153.76.167 has been assigned a threat score of 175/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

User-Agent AnomalyPath Enumeration

📊 Threat Analysis

IP address 129.153.76.167 has been traced to Phoenix, United States, operating on the network of Oracle Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 28 malicious requests from this address across a 5-day span, reflecting a sustained attack cadence of ~5.6 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 39 blocked IPs in our database, making it a notable source of malicious traffic. A score of 175/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

157.151.167.16 (300)150.136.253.162 (300)164.152.25.228 (300)158.101.39.212 (300)158.101.15.41 (300)View all →

🏢 Same network: AS31898

217.142.185.108 (310)158.178.231.159 (300)161.118.211.239 (300)147.15.149.40 (300)148.116.72.171 (300)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.

💡 DNS Amplification Attack Mechanics

DNS amplification exploits open resolvers to reflect and amplify traffic toward victims. A small query triggers a large response directed at the spoofed source IP, achieving amplification factors of 50x or more, overwhelming target bandwidth.

🔍 Check Any IP Address

Share this report: