
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +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 221.150.109.22: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Block scanning from 221.150.109.22: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 500 | Unknown | Low | Service on port 500 |
⚠️ 1 high-risk port detected on 221.150.109.22. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2025-32728 | NVD → |
| CVE-2019-6111 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2025-26465 | NVD → |
| CVE-2020-14145 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2008-3844 | NVD → |
| CVE-2018-15473 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2018-15919 | NVD → |
| CVE-2017-15906 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2020-15778 | NVD → |
| CVE-2018-20685 | NVD → |
| CVE-2019-6109 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2019-6110 | NVD → |
🔴 Security scanning identified 20 vulnerability entries on this host. This volume strongly suggests severely outdated software. 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.
221.150.109.22 has been assigned a threat score of 95/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:
Our monitoring infrastructure has identified 221.150.109.22, geolocated to Geumcheon-gu, South Korea, operating on the network of Korea Telecom, as a source of suspicious network activity. The address has been active for 6 days in our monitoring system, producing 3 flagged requests at a rate of ~0.5/day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. Our records show 146 malicious IPs originating from South Korea, positioning it as a significant contributor to global threat activity. With a threat score of 95/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
Internet of Things devices are prime targets for botnet recruitment due to weak default credentials, infrequent updates, and always-on connectivity. Compromised IoT devices generate persistent scanning and attack traffic without their owners knowledge.