
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
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 49 malicious IPs from this autonomous system.
IP 108.54.120.32 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Address UA spoofing from 108.54.120.32: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
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.
108.54.120.32 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.
The following attack categories were identified:
IP address 108.54.120.32 has been traced to Ronkonkoma, United States, operating on the network of Verizon Communications. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 1 days, this IP generated 39 malicious requests, averaging approximately 39 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 36,338 flagged addresses, United States represents a major presence in our threat database. The score of 60/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.
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.
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.
GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.