ABUSE.MOM
THREAT REPORT

IP Threat Report
45.133.170.60

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 14:08:11
First seen: 2026-04-17 20:00:06
Last seen: 2026-05-01 13:00:05
140

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEBURSTREFERER
01

Geolocation & Classification

IP Address
45.133.170.60
Type
Residential
Country
🇬🇧 United Kingdom
City
London
ISP
Hivelocity Inc
Organization
Heficed
Autonomous System
AS61317 Hivelocity LLC
Hit Count
3
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 7Medium-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
Burst: 7 req / 2sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 175
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-04-17 20:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 7 (+60), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-05-01 13:00:05
Last malicious request observed
Total score reached: 140/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Hivelocity Inc
AS61317 · 🇬🇧 United Kingdom
06

Recommendations

Actions taken & recommended

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

🌊 Traffic Flood Defense

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

07

Neighbors in 45.133.170.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 (8)
PortServiceRiskDescription
3389RDPHighRemote Desktop Protocol — primary target for ransomware attacks
5432PostgreSQLHighPostgreSQL database — direct database access risk
6001UnknownLowService on port 6001
6002UnknownLowService on port 6002
6003UnknownLowService on port 6003
6004UnknownLowService on port 6004
6262UnknownLowService on port 6262
9001UnknownLowService on port 9001

⚠️ 2 high-risk ports detected on 45.133.170.60. Exposed RDP (3389) is the #1 entry point for ransomware attacks. These services should not be publicly accessible without strict firewall rules.

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.

⛔ LISTED
zen.spamhaus.org
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

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

Path EnumerationRequest Flooding

📊 Threat Analysis

The address 45.133.170.60 originates from London, United Kingdom, operating on the network of Hivelocity Inc. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 13 days in our monitoring system, producing 3 flagged requests at a rate of ~0.2/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. United Kingdom currently accounts for 164 blocked IPs in our database, making it a significant source of malicious traffic. A score of 140/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 United Kingdom

104.28.240.60 (340)104.28.208.60 (340)91.230.225.3 (305)45.86.203.224 (305)45.86.203.35 (305)View all →

🏢 Same network: AS61317

45.133.170.121 (215)2.57.23.214 (215)102.165.5.113 (200)45.8.255.47 (200)102.165.1.97 (200)View all →
12

Security Intelligence

💡 Prototype Pollution Attacks

Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

🔍 Check Any IP Address

Share this report: