IP Threat Report
23.106.201.123
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Foreign referer | Referer from unrelated external domain | +10 | |
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 | |
| 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 23.106.201.123 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
🔎 Path Enumeration Protection
Block scanning from 23.106.201.123: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🤖 User-Agent Anomaly Defense
IP 23.106.201.123 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
📧 Spam Protection
Enable CAPTCHA on all public forms. Add honeypot fields. Rate-limit submissions to 3 per minute per IP. Deploy Akismet or CleanTalk.
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
23.106.201.123 has been assigned a threat score of 100/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
23.106.201.123 is registered in Seattle, United States, operating on the network of Leaseweb USA, Inc.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 866 malicious requests from this address across a 10-day span, reflecting a sustained attack cadence of ~86.6 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 103 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 100/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.
Related Threats
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.214.122 (350)103.215.74.213 (340)103.168.66.237 (340)34.187.158.4 (340)View all →Security Intelligence
💡 HTTP Header Analysis for Threat Detection
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
💡 Remote Code Execution (RCE)
RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.