
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 5 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 5 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 |
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 146.19.24.209: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
IP 146.19.24.209 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 146.19.24.209 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 135 | Unknown | Low | Service on port 135 |
| 445 | SMB | Critical | SMB file sharing — high-risk for EternalBlue and ransomware |
| 5985 | Unknown | Low | Service on port 5985 |
⚠️ 1 high-risk port detected on 146.19.24.209. SMB (445) exposure is associated with worm propagation and EternalBlue exploits. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2020-0796 | NVD → |
🔴 Security scanning identified 1 vulnerability entries on this host. Even a small number of CVEs can represent significant risk. Consult NVD advisories for details.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
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.
146.19.24.209 has been assigned a threat score of 225/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:
Our monitoring infrastructure has identified 146.19.24.209, geolocated to Warsaw, Poland, operating on the network of MEVSPACE sp. z o.o., as a source of suspicious network activity. During its 19-day observation window, we recorded 72 hostile requests from this IP — roughly 3.8 per day on average. 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. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. A score of 225/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.
Analyzing network flows (NetFlow, sFlow, IPFIX) provides visibility into traffic patterns without inspecting packet contents. Flow data reveals scanning activity, data exfiltration, lateral movement, and command-and-control channels at scale.