IP Threat Report
13.213.67.131
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst 39/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 92/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 21 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| 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 13.213.67.131 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 13.213.67.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Directory Scan Defense
IP 13.213.67.131 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Traffic Flood Defense
IP 13.213.67.131 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
🤖 Bot Detection
Address UA spoofing from 13.213.67.131: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Neighbors in 13.213.67.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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
13.213.67.131 has been assigned a threat score of 228/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 13.213.67.131, located in Singapore, Singapore, operating on the network of Amazon Technologies Inc., has been classified as malicious by our automated threat scoring engine. Over a period of 2 days, this IP generated 80 malicious requests, averaging approximately 40 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Singapore currently accounts for 116 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 228/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Related Threats
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.
💡 Botnet Command and Control Evolution
Botnet C2 infrastructure has evolved from centralized IRC channels to resilient peer-to-peer networks, domain generation algorithms, and blockchain-based communication. This evolution makes botnet takedowns increasingly difficult and expensive.