ABUSE.MOM
THREAT REPORT

IP Threat Report
154.53.62.130

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 09:04:21
First seen: 2026-03-27 02:00:07
Last seen: 2026-03-27 02:00:07
65

⛔ Verdict: BLOCK

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

BOT_UAUA_CHANGED
01

Geolocation & Classification

IP Address
154.53.62.130
Type
Hosting
Country
🇺🇸 United States
City
Seattle
ISP
Contabo Inc
Organization
Contabo Inc
Autonomous System
AS40021 Contabo Inc.
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: pythonKnown bot/crawler User-Agent detected+40
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Σ = 65
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-03-27 02:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: python (+40), UA changed for same IP (+25)
2026-03-27 02:00:07
Last malicious request observed
Total score reached: 65/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Contabo Inc
AS40021 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 154.53.62.130 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

🤖 User-Agent Anomaly Defense

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

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (4)
PortServiceRiskDescription
111UnknownLowService on port 111
443HTTPSLowHTTPS web server — encrypted web traffic
10250UnknownLowService on port 10250
31337UnknownLowService on port 31337
Hostnames: vmi2546429.contaboserver.net
PTR: vmi2546429.contaboserver.net

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.

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

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

10

Threat Analysis

154.53.62.130 has been assigned a threat score of 65/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 154.53.62.130 to malicious activity originating from Seattle, United States, operating on the network of Contabo Inc. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. Detected suspicious User-Agent anomalies including empty, forged, or rapidly rotating UA strings — characteristic of automated scanning tools. United States currently accounts for 118 blocked IPs in our database, making it a significant source of malicious traffic. The score of 65/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS40021

147.93.141.35 (305)212.28.177.3 (280)217.216.65.202 (270)217.216.67.33 (210)86.48.30.248 (195)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Subnet-Level vs IP-Level Blocking

When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.

🔍 Check Any IP Address

Share this report: