
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 14 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
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 61.75.19.219: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
IP 61.75.19.219 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 |
|---|---|---|---|
| 21 | FTP | Medium | File Transfer Protocol — often targeted for anonymous login attacks |
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 1433 | MSSQL | High | Service on port 1433 |
| 3690 | Unknown | Low | Service on port 3690 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
⚠️ Network scanning reveals 1 dangerous service exposed on 61.75.19.219. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2024-38474 | NVD → |
| CVE-2020-15778 | NVD → |
| CVE-2025-66200 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2024-38476 | NVD → |
| CVE-2024-38472 | NVD → |
| CVE-2025-49812 | NVD → |
| CVE-2025-55753 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2012-4360 | NVD → |
| CVE-2019-6109 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2008-3844 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2024-27316 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2019-6111 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2024-38473 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2018-15473 | NVD → |
| CVE-2007-2768 | NVD → |
🔴 This host has 58 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
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.
61.75.19.219 has been assigned a threat score of 220/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
The address 61.75.19.219 originates from Geumcheon-gu, South Korea, operating on the network of Korea Telecom. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Two attack patterns were identified (User-Agent Anomaly and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 101 malicious IPs originating from South Korea, positioning it as a significant contributor to global threat activity. A score of 220/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.
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.
Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.