
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 364 | 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: 19 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 69 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 17 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 188 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 18 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 66 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 11 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 193 | Medium-risk: admin panels, config files | +60 | |
| Burst: 17 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 62 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 60 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 354 | Medium-risk: admin panels, config files | +60 | |
| Burst: 59 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 53 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 67 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 183 | Medium-risk: admin panels, config files | +60 | |
| Burst: 64 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 50 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 15 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 52 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 40.80.90.214: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Block scanning from 40.80.90.214: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
IP 40.80.90.214 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
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.
40.80.90.214 has been assigned a threat score of 280/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
40.80.90.214 is registered in Pune, India, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 8 malicious requests from this address across a 4-day span, reflecting a sustained attack cadence of ~2 requests per day. 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 combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. A score of 280/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.
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.
Open redirect vulnerabilities allow attackers to redirect users from trusted domains to malicious sites. While often underestimated, these flaws enable convincing phishing, token theft through redirect-based OAuth flows, and SSRF chains.