IP Threat Report
67.205.140.0
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 |
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 67.205.140.0 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 67.205.140.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
⚙️ General Security
Add 67.205.140.0 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
Neighbors in 67.205.140.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 |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 6379 | Redis | Critical | Redis in-memory database — frequently misconfigured without auth |
⚠️ Network scanning reveals 1 dangerous service exposed on 67.205.140.0. Open database ports suggest possible data exfiltration risk. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2025-26465 | NVD → |
| CVE-2008-3844 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2025-26466 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2023-51767 | NVD → |
🔴 This host has 6 known CVEs associated with its exposed services. Multiple vulnerabilities suggest gaps in patch management. Review each CVE in the NVD database.
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
67.205.140.0 has been assigned a threat score of 100/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
📊 Threat Analysis
The address 67.205.140.0 originates from North Bergen, United States, operating on the network of DigitalOcean, LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 1-day observation window, we recorded 2 hostile requests from this IP — roughly 2 per day on average. 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. With 129 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 100/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
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
💡 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.
💡 HTTP Request Smuggling
Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.