
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 262 | Medium-risk: admin panels, config files | +60 | |
| Burst: 46 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 157 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 899 | Medium-risk: admin panels, config files | +60 | |
| Burst: 90 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 200 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 258 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 48 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 164 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Burst: 45 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 148 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 38 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 123 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 52 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 177 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 175 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 33 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 93 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 54 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 180 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 387 | Medium-risk: admin panels, config files | +60 | |
| Burst: 49 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 50 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 172 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 166 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 32 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 106 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 174 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 59 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 60 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 58 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 384 | Medium-risk: admin panels, config files | +60 | |
| Burst: 162 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 56 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 53 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 192 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 178 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 43 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 141 req / 10s | Abnormally fast request rate — automated scanning | +35 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Address UA spoofing from 72.146.30.147: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 72.146.30.147.
Block scanning from 72.146.30.147: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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.
72.146.30.147 has been assigned a threat score of 245/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 intelligence analysis has linked 72.146.30.147 to malicious activity originating from Milan, Italy, operating on the network of BellSouth.net Inc.. The address has been under observation since its initial detection. Our sensors captured 25 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~25 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 129 flagged addresses, Italy represents a significant presence in our threat database. A score of 245/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
Cross-Origin Resource Sharing misconfigurations can expose sensitive APIs to unauthorized origins. Wildcard policies, reflected origins, and null origin allowlisting create vulnerabilities that attackers exploit for data theft and unauthorized actions.