ABUSE.MOM
THREAT REPORT

IP Threat Report
216.133.177.230

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 12:59:35
First seen: 2026-03-28 19:00:10
Last seen: 2026-03-28 19:00:10
120

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTREFERER
01

Geolocation & Classification

IP Address
216.133.177.230
Type
Residential
Country
🇺🇸 United States
City
Lanham-Seabrook
ISP
RCN
Organization
GTT Americas
Autonomous System
AS6079 RCN
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 4Medium-risk: admin panels, config files+40
Burst: 43 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 59 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 120
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-03-28 19:00:10
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 4 (+40), Burst: 43 req / 2s (+35), Burst: 59 req / 10s (+35)
2026-03-28 19:00:10
Last malicious request observed
Total score reached: 120/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

RCN
AS6079 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 216.133.177.230 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 216.133.177.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Traffic Flood Defense

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

07

Neighbors in 216.133.177.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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

216.133.177.230 has been assigned a threat score of 120/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 216.133.177.230, geolocated to Lanham-Seabrook, United States, operating on the network of RCN, as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. Our records show 183 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 120/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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 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: AS6079

161.115.232.28 (130)161.115.238.90 (130)216.133.177.229 (130)161.115.235.244 (130)161.115.239.92 (130)View all →
12

Security Intelligence

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 File Upload Vulnerabilities

Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.

🔍 Check Any IP Address

Share this report: