ABUSE.MOM
THREAT REPORT

IP Threat Report
23.158.233.122

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:18:10
First seen: 2026-03-27 19:00:05
Last seen: 2026-05-30 07:15:48
165

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 165/100. Total malicious requests observed: 1041.

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
23.158.233.122
Type
Hosting
Country
🇺🇸 United States
City
Chicago
ISP
tzulo, inc.
Organization
Cloudfanatic.NET
Autonomous System
AS11878 tzulo, inc.
Hit Count
1041
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 5/2sAbnormally fast request rate — automated scanning+35
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 10Medium-risk: admin panels, config files+60
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger medium hits: 4Medium-risk: admin panels, config files+40
Danger medium hits: 6Medium-risk: admin panels, config files+60
Danger medium hits: 8Medium-risk: admin panels, config files+60
Foreign refererReferer from unrelated external domain+10
Foreign referer seenReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 410
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-03-27 19:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 5/2s (+35), Burst: 5 req / 2s (+35)
2026-05-30 07:15:48
Last malicious request observed
Total score reached: 165/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

tzulo, inc.
AS11878 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 23.158.233.122 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 23.158.233.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

IP 23.158.233.122 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

IP 23.158.233.122 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🤖 User-Agent Anomaly Defense

IP 23.158.233.122 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

07

Neighbors in 23.158.233.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

23.158.233.122 has been assigned a threat score of 165/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

23.158.233.122 is registered in Chicago, United States, operating on the network of tzulo, inc.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 63-day observation window, we recorded 1,041 hostile requests from this IP — roughly 16.5 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. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. United States currently accounts for 141 blocked IPs in our database, making it a significant source of malicious traffic. At 165/100, this is an extremely high-risk address. All traffic should be considered hostile.

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.

11

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 →

🏢 Same network: AS11878

68.235.40.3 (225)23.234.90.76 (223)23.234.88.112 (190)68.235.46.219 (180)162.212.153.56 (165)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Backup and Recovery Against Ransomware

Immutable, offline backups remain the most effective defense against ransomware. The 3-2-1 rule — three copies on two media types with one offsite — combined with regular recovery testing ensures business continuity after encryption attacks.

🔍 Check Any IP Address

Share this report: