IP Threat Report
146.190.116.67
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: spider | Known bot/crawler User-Agent detected | +40 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Burst: 29 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 51 req / 10s | Abnormally fast request rate — automated scanning | +35 |
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 146.190.116.67 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 Bot Detection
Address UA spoofing from 146.190.116.67: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 146.190.116.67.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| CVE ID | Link |
|---|---|
| CVE-2013-4365 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2012-3526 | NVD → |
| CVE-2024-38477 | NVD → |
| CVE-2024-38474 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2025-53020 | NVD → |
| CVE-2025-65082 | NVD → |
| CVE-2012-4001 | NVD → |
| CVE-2009-2299 | NVD → |
| CVE-2024-39573 | NVD → |
| CVE-2024-47252 | NVD → |
| CVE-2024-38475 | NVD → |
| CVE-2011-1176 | NVD → |
| CVE-2025-49812 | NVD → |
| CVE-2025-66200 | NVD → |
| CVE-2023-38709 | NVD → |
| CVE-2024-24795 | NVD → |
| CVE-2024-36387 | NVD → |
| CVE-2024-27316 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2024-43394 | NVD → |
| CVE-2024-38472 | NVD → |
🔴 This host has 37 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. 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
146.190.116.67 has been assigned a threat score of 260/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 146.190.116.67, located in Santa Clara, United States, operating on the network of DigitalOcean, LLC, has been classified as malicious by our automated threat scoring engine. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per 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. Two attack patterns were identified (User-Agent Anomaly and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 28 malicious IPs originating from United States, positioning it as a notable contributor to global threat activity. With a threat score of 260/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
168.144.34.140 (295)167.99.61.194 (270)64.227.107.170 (255)165.227.53.4 (245)64.23.160.23 (235)View all →Security Intelligence
💡 User-Agent Analysis Techniques
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.
💡 Security Header Best Practices
HTTP security headers provide defense-in-depth with minimal implementation effort. Key headers include Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy, each addressing specific attack vectors.