ABUSE.MOM
THREAT REPORT

IP Threat Report
168.144.43.14

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 21:21:35
First seen: 2026-03-31 14:00:07
Last seen: 2026-04-01 04:00:07
180

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404
01

Geolocation & Classification

IP Address
168.144.43.14
Type
Hosting
Country
🇺🇸 United States
City
Broomfield
ISP
DigitalOcean
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
44
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 16Medium-risk: admin panels, config files+60
Burst: 9 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 16 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 8 req / 2sAbnormally fast request rate — automated scanning+35
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 10 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 250
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-31 14:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 1 (+25), Danger medium hits: 16 (+60), Burst: 9 req / 2s (+35)
2026-04-01 04:00:07
Last malicious request observed
Total score reached: 180/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean
AS14061 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 168.144.43.14.

🔎 Directory Scan Defense

IP 168.144.43.14 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

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
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
zen.spamhaus.org
✓ 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

168.144.43.14 has been assigned a threat score of 180/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 FloodingPath Enumeration

📊 Threat Analysis

Network traffic from 168.144.43.14, located in Broomfield, United States, operating on the network of DigitalOcean, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 44 hostile requests from this IP — roughly 44 per day on average. 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 Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 128 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 180/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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

129.212.237.216 (308)168.144.34.140 (295)170.64.203.182 (280)161.35.89.38 (273)64.226.94.117 (273)View all →
12

Security Intelligence

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

💡 Data Center IP Reputation

IPs originating from data centers and hosting providers account for a disproportionate amount of malicious traffic. Compromised VPS instances, bulletproof hosting, and abused trial accounts create persistent attack infrastructure that can be difficult to shut down.

🔍 Check Any IP Address

Share this report: