ABUSE.MOM
THREAT REPORT

IP Threat Report
31.6.41.4

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 01:26:05
First seen: 2026-08-08 21:53:55
Last seen: 2026-08-09 04:17:00
210

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHREDIRECT_PROBEREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
31.6.41.4
Type
VPN
Country
🇨🇭 Switzerland
City
Zurich
ISP
YHC
Organization
Unknown
Autonomous System
AS22363 Powerhouse Management, Inc.
Hit Count
228
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 10/2sAbnormally fast request rate — automated scanning+35
Burst 11/10sAbnormally fast request rate — automated scanning+35
Burst 11/2sAbnormally fast request rate — automated scanning+35
Burst 12/10sAbnormally fast request rate — automated scanning+35
Burst 5/2sAbnormally fast request rate — automated scanning+35
Burst 7/2sAbnormally fast request rate — automated scanning+35
Burst 8/2sAbnormally fast request rate — automated scanning+35
Burst 9/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger medium hits: 3Medium-risk: admin panels, config files+30
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 510
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-08-08 21:53:55
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 10/2s (+35), Burst 11/10s (+35), Burst 11/2s (+35)
2026-08-09 04:17:00
Last malicious request observed
Total score reached: 210/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

YHC
AS22363 · 🇨🇭 Switzerland
06

Recommendations

Actions taken & recommended

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

🌊 Traffic Flood Defense

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

🔎 Path Enumeration Protection

Block scanning from 31.6.41.4: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 Bot Detection

Address UA spoofing from 31.6.41.4: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 31.6.41.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
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
bl.blocklist.de
✓ Clean
dnsbl.dronebl.org
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

31.6.41.4 has been assigned a threat score of 210/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Request FloodingPath EnumerationUser-Agent Anomaly

📊 Threat Analysis

31.6.41.4 is registered in Zurich, Switzerland, operating on the network of YHC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 228 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~228 requests per day. The address operates as a VPN/proxy exit node. Attackers route traffic through anonymizing services to obscure their real location and evade IP-based security controls. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With a threat score of 210/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

11

Related Threats

🇨🇭 Top threats from Switzerland

31.6.41.11 (220)31.6.41.16 (160)31.6.41.3 (160)View all →

🏢 Same network: AS22363

128.90.161.1 (265)128.90.128.3 (265)128.90.141.19 (230)128.90.141.2 (230)128.90.145.15 (220)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.

💡 Subdomain Takeover Vulnerabilities

Subdomain takeover occurs when DNS records point to decommissioned services. Attackers claim the abandoned resource and serve content under the trusted domain, enabling cookie theft, phishing, and reputation damage.

🔍 Check Any IP Address

Share this report: