ABUSE.MOM
THREAT REPORT

IP Threat Report
45.131.194.120

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:06:06
First seen: 2026-05-26 21:42:55
Last seen: 2026-05-30 08:04:49
160

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404UA_CHANGED
01

Geolocation & Classification

IP Address
45.131.194.120
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
336
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 270
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-05-26 21:42:55
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Danger medium hits: 1 (+10)
2026-05-30 08:04:49
Last malicious request observed
Total score reached: 160/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 45.131.194.120 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.131.194.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

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

🤖 User-Agent Anomaly Defense

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

07

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

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

10

Threat Analysis

45.131.194.120 has been assigned a threat score of 160/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 EnumerationUser-Agent Anomaly

📊 Threat Analysis

Network traffic from 45.131.194.120, located in an unknown location, has been classified as malicious by our automated threat scoring engine. Our sensors captured 336 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~112 requests per day. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. With a threat score of 160/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

11

Related Threats

🇤🇤 Top threats from ??

View all →
12

Security Intelligence

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

💡 VPN Exit Node Reputation

VPN exit nodes aggregate traffic from many users, creating mixed reputation profiles. While legitimate users seek privacy, attackers exploit VPN services to anonymize malicious activity, making IP-based blocking of VPN nodes a complex policy decision.

🔍 Check Any IP Address

Share this report: