ABUSE.MOM
THREAT REPORT

IP Threat Report
178.175.134.123

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 11:44:48
First seen: 2026-02-26 13:00:06
Last seen: 2026-03-02 09:00:06
165

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERERBURSTUA_CHANGED
01

Geolocation & Classification

IP Address
178.175.134.123
Type
Residential
Country
🇲🇩 MD
City
Chisinau
ISP
Trabia SRL
Organization
Trabia SRL
Autonomous System
AS43289 Trabia SRL
Hit Count
4
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 4Medium-risk: admin panels, config files+40
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
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger medium hits: 8Medium-risk: admin panels, config files+60
Σ = 205
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-02-26 13:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 4 (+40), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-03-02 09:00:06
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

Trabia SRL
AS43289 · 🇲🇩 MD
06

Recommendations

Actions taken & recommended

  • IP 178.175.134.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 178.175.134.123: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 178.175.134.123.

🤖 User-Agent Anomaly Defense

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

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

178.175.134.123 has been assigned a threat score of 165/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

178.175.134.123 is registered in Chisinau, MD, operating on the network of Trabia SRL. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 4 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~1.3 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. With 11 flagged addresses, MD represents a notable presence in our threat database. A score of 165/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 MD

5.63.19.3 (215)178.175.140.218 (215)85.121.5.215 (175)178.175.140.221 (165)91.228.110.58 (145)View all →

🏢 Same network: AS43289

178.175.140.218 (215)178.175.140.221 (165)178.175.129.44 (70)View all →
12

Security Intelligence

💡 File Upload Vulnerabilities

Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.

💡 Data Breach Impact Assessment

The impact of data breaches extends beyond immediate financial losses. Regulatory fines, legal liability, reputational damage, and customer churn create long-term costs that often exceed the direct costs of incident response and remediation.

🔍 Check Any IP Address

Share this report: