ABUSE.MOM
THREAT REPORT

IP Threat Report
5.180.179.129

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-24 23:58:14
First seen: 2026-09-30 22:51:50
Last seen: 2026-10-03 23:58:38
235

⛔ Verdict: BLOCK

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

BOT_UABURSTDANGER_PATH
01

Geolocation & Classification

IP Address
5.180.179.129
Type
Hosting
Country
🇱🇧 LB
City
Beirut
ISP
GSL Networks Pty LTD
Organization
GSL Networks Pty LTD
Autonomous System
AS137409 GSL Networks Pty LTD
Hit Count
50
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 14/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 19Medium-risk: admin panels, config files+60
Danger strong hits: 13High-risk paths: shells, RCE vectors, exploits+100
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Σ = 235
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-09-30 22:51:50
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 14/10s (+35), Danger medium hits: 19 (+60), Danger strong hits: 13 (+100)
2026-10-03 23:58:38
Last malicious request observed
Total score reached: 235/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

GSL Networks Pty LTD
AS137409 · 🇱🇧 LB

We have detected 361 malicious IPs from this autonomous system.

View all IPs from AS137409 →
06

Recommendations

Actions taken & recommended

  • IP 5.180.179.129 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 5.180.179.0/24
  • 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 5.180.179.129.

🤖 Bot Detection

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

07

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

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

10

Threat Analysis

5.180.179.129 has been assigned a threat score of 235/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Network traffic from 5.180.179.129, located in Beirut, LB, operating on the network of GSL Networks Pty LTD, has been classified as malicious by our automated threat scoring engine. The address has been active for 3 days in our monitoring system, producing 50 flagged requests at a rate of ~16.7/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. LB currently accounts for 38 blocked IPs in our database, making it a notable source of malicious traffic. A score of 235/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 LB

5.180.179.128 (295)5.180.179.188 (245)194.126.137.46 (103)185.104.244.227 (103)185.104.253.143 (103)View all →

🏢 Same network: AS137409

5.180.179.11 (340)212.30.37.68 (305)85.203.23.219 (305)147.90.177.238 (305)141.11.36.44 (305)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.

💡 Autonomous System Analysis

Analyzing attack patterns at the AS (Autonomous System) level reveals which networks harbor the most malicious activity. Some ASes have abuse rates orders of magnitude higher than average, indicating lax enforcement of acceptable use policies.

🔍 Check Any IP Address

Share this report: