
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
We have detected 92 malicious IPs from this autonomous system.
Add 172.58.243.197 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
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.
172.58.243.197 has been assigned a threat score of 65/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
Our monitoring infrastructure has identified 172.58.243.197, geolocated to Washington, United States, operating on the network of T-Mobile USA, Inc., as a source of suspicious network activity. Over a period of 13 days, this IP generated 195 malicious requests, averaging approximately 15 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. United States currently accounts for 36,329 blocked IPs in our database, making it a major source of malicious traffic. The score of 65/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.
Cloud platforms provide attackers with elastic, disposable infrastructure. Free tier accounts, stolen credit cards, and compromised cloud credentials enable rapid deployment of attack infrastructure that can scale to millions of requests and disappear within hours.
CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.