ABUSE.MOM
THREAT REPORT

IP Threat Report
45.134.20.143

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:41:30
First seen: 2026-07-15 07:40:19
Last seen: 2026-07-26 04:06:57
255

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404UA_CHANGED
01

Geolocation & Classification

IP Address
45.134.20.143
Type
VPN
Country
🇦🇺 Australia
City
Sydney
ISP
VPN
Organization
VPN-Consumer-AU
Autonomous System
AS396356 Latitude.sh
Hit Count
547
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 12/10sAbnormally fast request rate — automated scanning+35
Burst 20/10sAbnormally fast request rate — automated scanning+35
Burst 22/10sAbnormally fast request rate — automated scanning+35
Burst 27/10sAbnormally fast request rate — automated scanning+35
Burst 28/10sAbnormally fast request rate — automated scanning+35
Burst 6/2sAbnormally fast request rate — automated scanning+35
Burst 8/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 12Medium-risk: admin panels, config files+60
Danger medium hits: 49Medium-risk: admin panels, config files+60
Danger medium hits: 969Medium-risk: admin panels, config files+60
Danger strong hits: 101High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 102High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 126High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 372High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 925
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-07-15 07:40:19
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 12/10s (+35), Burst 20/10s (+35)
2026-07-26 04:06:57
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

VPN
AS396356 · 🇦🇺 Australia
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

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

🤖 Bot Detection

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

07

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

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

10

Threat Analysis

45.134.20.143 has been assigned a threat score of 255/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 EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 45.134.20.143 has been traced to Sydney, Australia, operating on the network of VPN. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 10-day observation window, we recorded 547 hostile requests from this IP — roughly 54.7 per day on average. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 87 flagged addresses, Australia represents a notable presence in our threat database. A score of 255/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 Australia

45.134.20.152 (280)45.134.20.92 (280)45.134.20.96 (280)45.134.20.126 (255)45.134.20.130 (255)View all →

🏢 Same network: AS396356

45.134.20.152 (280)45.134.20.92 (280)45.134.20.96 (280)45.134.20.126 (255)45.134.20.130 (255)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.

💡 Content Security Policy Implementation

Content Security Policy headers instruct browsers to restrict resource loading, mitigating XSS and data injection attacks. Properly configured CSP policies prevent inline script execution, restrict iframe embedding, and control which domains can serve content.

🔍 Check Any IP Address

Share this report: