ABUSE.MOM
THREAT REPORT

IP Threat Report
216.41.233.198

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:56:21
First seen: 2026-02-19 01:00:06
Last seen: 2026-03-20 22:00:07
105

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
216.41.233.198
Type
Residential
Country
🇺🇸 United States
City
Chicago
ISP
Sprious LLC
Organization
Blazing SEO, LLC
Autonomous System
AS64267 Sprious LLC
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 6Medium-risk: admin panels, config files+60
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Danger medium hits: 7Medium-risk: admin panels, config files+60
Σ = 165
03

Observed Activity

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

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

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

04

Timeline

2026-02-19 01:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 6 (+60), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-03-20 22:00:07
Last malicious request observed
Total score reached: 105/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Sprious LLC
AS64267 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 216.41.233.198 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 216.41.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 216.41.233.198 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

07

Neighbors in 216.41.233.0/24

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

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (2)
PortServiceRiskDescription
4444UnknownLowService on port 4444
60000UnknownLowService on port 60000
KNOWN VULNERABILITIES (CVE) (27)
CVE IDLink
CVE-2021-28116NVD →
CVE-2023-46847NVD →
CVE-2021-31807NVD →
CVE-2024-37894NVD →
CVE-2022-41317NVD →
CVE-2025-59362NVD →
CVE-2024-45802NVD →
CVE-2023-46728NVD →
CVE-2023-49288NVD →
CVE-2021-28652NVD →
CVE-2024-25111NVD →
CVE-2021-28651NVD →
CVE-2021-28662NVD →
CVE-2021-33620NVD →
CVE-2025-62168NVD →
CVE-2021-31808NVD →
CVE-2021-46784NVD →
CVE-2023-5824NVD →
CVE-2023-50269NVD →
CVE-2023-46846NVD →
CVE-2023-49285NVD →
CVE-2023-46724NVD →
CVE-2022-41318NVD →
CVE-2021-31806NVD →
CVE-2024-25617NVD →
+2 more

🔴 This host has 27 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.

DETECTED TECHNOLOGIES
squid-cache:squid:4.14
Hostnames: host-216-41-233-198.static.sprious.com
PTR: host-216-41-233-198.static.sprious.com

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

✓ Clean
Spamhaus ZEN

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

10

Threat Analysis

216.41.233.198 has been assigned a threat score of 105/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:

Path Enumeration

📊 Threat Analysis

Network traffic from 216.41.233.198, located in Chicago, United States, operating on the network of Sprious LLC, has been classified as malicious by our automated threat scoring engine. Over a period of 29 days, this IP generated 2 malicious requests, averaging approximately 0.1 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 202 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 105/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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.

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: AS64267

66.146.236.62 (200)216.213.28.68 (200)192.171.87.62 (200)162.244.145.212 (180)199.34.84.33 (180)View all →
12

Security Intelligence

💡 Vulnerability Scanning Explained

Vulnerability scanning is the automated process of probing web applications for known weaknesses. Attackers use tools like Nuclei, Nikto, and ZAP to test thousands of hosts per hour, looking for exposed configuration files, outdated software, and default credentials.

💡 GeoIP Blocking Considerations

Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.

🔍 Check Any IP Address

Share this report: