IP Threat Report
38.127.172.116
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Form spam: no_js_check | Spam/malware keywords in request content | +0 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 38.127.172.116 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 38.127.172.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
📧 Spam Protection
Enable CAPTCHA on all public forms. Add honeypot fields. Rate-limit submissions to 3 per minute per IP. Deploy Akismet or CleanTalk.
Neighbors in 38.127.172.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Open Ports & Services
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 |
| CVE ID | Link |
|---|---|
| CVE-2016-6292 | NVD → |
| CVE-2022-31629 | NVD → |
| CVE-2016-2161 | NVD → |
| CVE-2015-3414 | NVD → |
| CVE-2022-37436 | NVD → |
| CVE-2014-8109 | NVD → |
| CVE-2014-4698 | NVD → |
| CVE-2021-44790 | NVD → |
| CVE-2016-7416 | NVD → |
| CVE-2018-10546 | NVD → |
| CVE-2016-4537 | NVD → |
| CVE-2017-11147 | NVD → |
| CVE-2015-8867 | NVD → |
| CVE-2018-14851 | NVD → |
| CVE-2015-3330 | NVD → |
| CVE-2015-6838 | NVD → |
| CVE-2014-3487 | NVD → |
| CVE-2014-3479 | NVD → |
| CVE-2017-15715 | NVD → |
| CVE-2018-5711 | NVD → |
| CVE-2014-3538 | NVD → |
| CVE-2014-0238 | NVD → |
| CVE-2017-11144 | NVD → |
| CVE-2022-23943 | NVD → |
| CVE-2015-4604 | NVD → |
🔴 Security scanning identified 331 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.
Blacklist Status (DNSBL)
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.
Threat Analysis
38.127.172.116 has been assigned a threat score of 70/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.
📊 Threat Analysis
IP address 38.127.172.116 has been traced to Washington, United States, operating on the network of Cogent Communications. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Our records show 186 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. The score of 70/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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.
Related Threats
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →Security Intelligence
💡 SQL Injection Campaigns
SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.
💡 API Abuse and Enumeration
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.