ABUSE.MOM
THREAT REPORT

IP Threat Report
173.44.213.127

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-05 05:21:59
First seen: 2026-06-17 04:13:13
Last seen: 2026-07-05 04:01:55
130

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
173.44.213.127
Type
Unknown
Country
🇺🇸 United States
City
Seattle
ISP
Eonix Corporation
Organization
Eonix Corporation
Autonomous System
Unknown
Hit Count
1524
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 2Medium-risk: admin panels, config files+20
Directory ScanBehavioral anomaly detected by automated analysis+0
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 65
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-17 04:13:13
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 2 (+20), Directory Scan
2026-07-05 04:01:55
Last malicious request observed
Total score reached: 130/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

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

07

Neighbors in 173.44.213.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
spam.dnsbl.sorbs.net
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

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

Path Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 173.44.213.127, geolocated to Seattle, United States, operating on the network of Eonix Corporation, as a source of suspicious network activity. Our sensors captured 1,524 malicious requests from this address across a 17-day span, reflecting a sustained attack cadence of ~89.6 requests per day. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United States currently accounts for 104 blocked IPs in our database, making it a significant source of malicious traffic. At 130/100, this is an extremely high-risk address. All traffic should be considered hostile.

11

Related Threats

🇺🇸 Top threats from United States

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

Security Intelligence

💡 Vulnerability Scanning Explained

Vulnerability scanning is the automated process of probing web applications for known weaknesses. Attackers use tools like Nuclei, Nikto, and ZAP to test thousands of hosts per hour, looking for exposed configuration files, outdated software, and default credentials.

💡 Prototype Pollution Attacks

Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.

🔍 Check Any IP Address

Share this report: