
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst 13/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 14/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 28/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 38/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 40/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 43/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 44/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 45/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 46/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 48/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 49/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 84/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 118 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 136 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 165 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 166 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 250 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 251 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 252 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 722 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 752 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 98 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 99 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 268 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 272 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 48 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 56 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 74 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 97 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 99 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 4.228.83.111 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 4.228.83.111 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Address UA spoofing from 4.228.83.111: 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.
4.228.83.111 has been assigned a threat score of 280/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 4.228.83.111 to malicious activity originating from São Paulo, Brazil, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. During its 7-day observation window, we recorded 1,304 hostile requests from this IP — roughly 186.3 per day on average. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 12 flagged addresses, Brazil represents a notable presence in our threat database. With a threat score of 280/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.
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.
The RaaS model allows technically unskilled criminals to deploy sophisticated ransomware through affiliate programs. Operators provide the malware, infrastructure, and negotiation services, taking a percentage of ransom payments from their affiliates.