IP Threat Report
99.99.17.133
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 |
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
Recommendations
Actions taken & recommended
- IP 99.99.17.133 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
⚙️ Defensive Recommendations
Block 99.99.17.133 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
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
99.99.17.133 has been assigned a threat score of 60/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.
📊 Threat Analysis
The address 99.99.17.133 originates from Palm Bay, United States, operating on the network of AT&T Enterprises, LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 197 malicious requests from this address across a 23-day span, reflecting a sustained attack cadence of ~8.6 requests per day. With 101 flagged addresses, United States represents a significant presence in our threat database. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
Related Threats
🇺🇸 Top threats from United States
104.28.246.115 (350)103.215.74.213 (340)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →Security Intelligence
💡 Race Condition Vulnerabilities
Race conditions occur when application behavior depends on the timing of concurrent operations. Attackers exploit these timing windows to bypass limits, duplicate transactions, or escalate privileges by sending carefully timed parallel requests.
💡 Threat Score Calculation Methods
Threat scoring combines multiple signals — request patterns, known signatures, IP reputation, geographic risk, and behavioral analysis — into a single actionable metric. Weighted scoring models allow tuning sensitivity to balance security with usability.