IP Threat Report
39.173.76.5
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Burst 27/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 9/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA bot: curl | Known bot/crawler User-Agent detected | +40 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 39.173.76.5 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 39.173.76.5.
🔎 Path Enumeration Protection
Block scanning from 39.173.76.5: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🤖 Bot Detection
Address UA spoofing from 39.173.76.5: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
39.173.76.5 has been assigned a threat score of 195/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 39.173.76.5, located in Hangzhou, China, operating on the network of China Mobile Communications Corporation, has been classified as malicious by our automated threat scoring engine. Our sensors captured 59 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~29.5 requests per day. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Our records show 102 malicious IPs originating from China, positioning it as a significant contributor to global threat activity. With a threat score of 195/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
Related Threats
🇨🇳 Top threats from China
180.184.55.222 (340)101.200.57.251 (310)118.25.236.48 (280)47.93.233.71 (273)120.48.70.170 (273)View all →🏢 Same network: AS56041
View all →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.
💡 Behavioral Analysis vs Signature Detection
Signature-based detection matches known attack patterns but misses novel threats. Behavioral analysis identifies anomalies in request patterns, timing, and volume, catching zero-day attacks that signatures cannot recognize.