ABUSE.MOM
THREAT REPORT

IP Threat Report
130.254.112.220

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 13:20:46
First seen: 2026-06-06 06:54:59
Last seen: 2026-06-23 05:03:41
75

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

IP Address
130.254.112.220
Type
Unknown
Country
🇺🇸 United States
City
Los Angeles
ISP
Blazing SEO
Organization
Blazing SEO
Autonomous System
Unknown
Hit Count
113
02

Detection Signatures

SignatureDescriptionPointsSeverity
Directory ScanBehavioral anomaly detected by automated analysis+0
Σ = 0
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-06-06 06:54:59
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Directory Scan
2026-06-23 05:03:41
Last malicious request observed
Total score reached: 75/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 130.254.112.220 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 130.254.112.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

⚙️ Defensive Recommendations

Block 130.254.112.220 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

07

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

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

10

Threat Analysis

130.254.112.220 has been assigned a threat score of 75/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

📊 Threat Analysis

Network traffic from 130.254.112.220, located in Los Angeles, United States, operating on the network of Blazing SEO, has been classified as malicious by our automated threat scoring engine. During its 16-day observation window, we recorded 113 hostile requests from this IP — roughly 7.1 per day on average. Our records show 110 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. The score of 75/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)103.215.74.213 (340)103.168.66.237 (340)34.187.158.4 (340)View all →
12

Security Intelligence

💡 Network Flow Analysis

Analyzing network flows (NetFlow, sFlow, IPFIX) provides visibility into traffic patterns without inspecting packet contents. Flow data reveals scanning activity, data exfiltration, lateral movement, and command-and-control channels at scale.

💡 TLS Certificate Misconfigurations

Expired, self-signed, or misconfigured TLS certificates create security vulnerabilities and trust issues. Certificate monitoring, automated renewal through ACME protocols, and proper certificate chain configuration prevent both security gaps and service disruptions.

🔍 Check Any IP Address

Share this report: