
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | 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 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger medium hits: 8 | Medium-risk: admin panels, config files | +60 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Block scanning from 38.154.110.185: 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 |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 1344 | Unknown | Low | Service on port 1344 |
| 3128 | Unknown | Low | Service on port 3128 |
| 8000 | Unknown | Low | Service on port 8000 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8800 | Unknown | Low | Service on port 8800 |
| 21242 | Unknown | Low | Service on port 21242 |
| 52931 | Unknown | Low | Service on port 52931 |
| CVE ID | Link |
|---|---|
| CVE-2023-46724 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2018-1000024 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2019-13345 | NVD → |
| CVE-2020-24606 | NVD → |
| CVE-2018-1000027 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2019-12525 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2019-12521 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2019-12528 | NVD → |
| CVE-2019-18678 | NVD → |
🔴 Security scanning identified 56 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.
38.154.110.185 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:
Our monitoring infrastructure has identified 38.154.110.185, geolocated to Buffalo, United States, operating on the network of B2 Net Solutions Inc., as a source of suspicious network activity. The address has been active for 27 days in our monitoring system, producing 12 flagged requests at a rate of ~0.4/day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 180 flagged addresses, United States represents a significant presence in our threat database. A score of 105/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.
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.
GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.