ABUSE.MOM
THREAT REPORT

IP Threat Report
153.54.180.120

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 08:19:31
First seen: 2026-10-18 07:53:53
Last seen: 2026-10-25 04:06:31
80

⛔ Verdict: BLOCK

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

BURSTREFERER
01

Geolocation & Classification

IP Address
153.54.180.120
Type
VPN
Country
🇺🇸 United States
City
Seattle
ISP
Packethub S.A.
Organization
PacketHub S.A
Autonomous System
AS272096 PACKETHUB S.A.
Hit Count
132
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 56/2sAbnormally fast request rate — automated scanning+35
Burst 57/10sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
Σ = 80
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-10-18 07:53:53
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 56/2s (+35), Burst 57/10s (+35), Foreign referer (+10)
2026-10-25 04:06:31
Last malicious request observed
Total score reached: 80/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Packethub S.A.
AS272096 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

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

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
zen.spamhaus.org
✓ Clean
psbl.surriel.com
✓ Clean
bl.blocklist.de
✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
cbl.abuseat.org
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

153.54.180.120 has been assigned a threat score of 80/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

The address 153.54.180.120 originates from Seattle, United States, operating on the network of Packethub S.A.. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 6 days, this IP generated 132 malicious requests, averaging approximately 22 requests per day. 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. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. United States currently accounts for 36,319 blocked IPs in our database, making it a major source of malicious traffic. At 80/100, this IP warrants immediate defensive action.

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 United States

104.28.246.115 (350)104.28.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS272096

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.

💡 Rate Limiting and Throttling Strategies

Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.

🔍 Check Any IP Address

Share this report: