
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst 112/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 118/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 132/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 140/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 152/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 155/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 40/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 46/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 49/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 51/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 58/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 114 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 124 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 296 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 298 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 372 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 447 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 99 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 22 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 28 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 38 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | 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.223.135.162 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 4.223.135.162.
Address UA spoofing from 4.223.135.162: 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.223.135.162 has been assigned a threat score of 280/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
Network traffic from 4.223.135.162, located in Gävle, Sweden, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. During its 7-day observation window, we recorded 1,072 hostile requests from this IP — roughly 153.1 per day on average. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Sweden currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. 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.
Command injection occurs when attackers insert operating system commands through application inputs. Successful exploitation grants direct server access, enabling data theft, malware installation, and lateral movement across networks.