
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 |
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 139.180.230.207: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Block scanning from 139.180.230.207: 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 |
|---|---|---|---|
| 4444 | Unknown | Low | Service on port 4444 |
| 8000 | Unknown | Low | Service on port 8000 |
| 60000 | Unknown | Low | Service on port 60000 |
| CVE ID | Link |
|---|---|
| CVE-2024-45802 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2021-28662 | NVD → |
🔴 Security scanning identified 30 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.
139.180.230.207 has been assigned a threat score of 105/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:
IP address 139.180.230.207 has been traced to New York, United States, operating on the network of Sprious LLC, Blazing SEO, LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 3 malicious requests from this address across a 40-day span, reflecting a sustained attack cadence of ~0.1 requests per day. 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. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 202 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 105/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.
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.
Monitoring dark web forums and marketplaces provides advance warning of planned attacks, leaked credentials, and compromised data. This intelligence feeds into proactive defense measures before attacks reach their targets.