IP Threat Report
140.245.50.113
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 18 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 10 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 11 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 5 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Burst: 29 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 9 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 11 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 31 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 15 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 30 req / 10s | Abnormally fast request rate — automated scanning | +35 |
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 140.245.50.113 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 140.245.50.113: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🔎 Path Enumeration Protection
Block scanning from 140.245.50.113: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 140.245.50.113 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
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
140.245.50.113 has been assigned a threat score of 265/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
Our monitoring infrastructure has identified 140.245.50.113, geolocated to Singapore, Singapore, operating on the network of Oracle Corporation, as a source of suspicious network activity. The address has been active for 30 days in our monitoring system, producing 78 flagged requests at a rate of ~2.6/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Our records show 125 malicious IPs originating from Singapore, positioning it as a significant contributor to global threat activity. With a threat score of 265/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.
Related Threats
Security Intelligence
💡 HTTP Header Analysis for Threat Detection
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
💡 Phishing Infrastructure Analysis
Modern phishing operations use sophisticated infrastructure including lookalike domains, valid TLS certificates, and evasion techniques like cloaking and geofencing. Analyzing this infrastructure reveals campaigns before they reach their targets.