ABUSE.MOM
THREAT REPORT

IP Threat Report
130.250.189.162

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-06 01:49:41
First seen: 2026-08-30 22:44:45
Last seen: 2026-09-06 01:06:27
205

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
130.250.189.162
Type
Residential
Country
🇺🇸 United States
City
Piscataway
ISP
X99
Organization
X99
Autonomous System
AS398991 X99
Hit Count
1117
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 10Medium-risk: admin panels, config files+60
Danger medium hits: 12Medium-risk: admin panels, config files+60
Danger medium hits: 14Medium-risk: admin panels, config files+60
Danger medium hits: 16Medium-risk: admin panels, config files+60
Danger medium hits: 18Medium-risk: admin panels, config files+60
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger medium hits: 20Medium-risk: admin panels, config files+60
Danger medium hits: 3Medium-risk: admin panels, config files+30
Danger medium hits: 4Medium-risk: admin panels, config files+40
Danger medium hits: 6Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 16High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 18High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 20High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 1540
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-08-30 22:44:45
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Danger medium hits: 1 (+10)
2026-09-06 01:06:27
Last malicious request observed
Total score reached: 205/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

X99
AS398991 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

Block scanning from 130.250.189.162: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

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
cbl.abuseat.org
✓ Clean
b.barracudacentral.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

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

Path Enumeration

📊 Threat Analysis

130.250.189.162 is registered in Piscataway, United States, operating on the network of X99. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 6 days in our monitoring system, producing 1,117 flagged requests at a rate of ~186.2/day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 101 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 205/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.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS398991

View all →
12

Security Intelligence

💡 Remote Code Execution (RCE)

RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.

💡 Edge Computing Attack Surface

Edge computing pushes processing closer to users but expands the attack surface. Edge nodes often run in less secure environments than centralized data centers, creating new opportunities for physical access attacks and supply chain compromises.

🔍 Check Any IP Address

Share this report: