ABUSE.MOM
THREAT REPORT

IP Threat Report
161.35.57.244

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 16:39:20
First seen: 2026-09-01 23:08:17
Last seen: 2026-09-20 02:10:38
60

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
161.35.57.244
Type
Hosting
Country
🇺🇸 United States
City
North Bergen
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
262
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Foreign refererReferer from unrelated external domain+10
Σ = 60
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-09-01 23:08:17
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger strong hits: 1 (+25), Foreign referer (+10)
2026-09-20 02:10:38
Last malicious request observed
Total score reached: 60/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇺🇸 United States

We have detected 7047 malicious IPs from this autonomous system.

View all IPs from AS14061 →
06

Recommendations

Actions taken & recommended

  • IP 161.35.57.244 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 161.35.57.0/24
  • 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 161.35.57.244: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

07

Neighbors in 161.35.57.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
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

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

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

161.35.57.244 is registered in North Bergen, United States, operating on the network of DigitalOcean, LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 18 days in our monitoring system, producing 262 flagged requests at a rate of ~14.6/day. 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 36,339 malicious IPs originating from United States, positioning it as a major contributor to global threat activity. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS14061

129.212.237.216 (308)168.144.34.140 (295)170.64.203.182 (280)159.223.199.244 (280)168.144.130.251 (280)View all →
12

Security Intelligence

💡 Brute Force Attack Mechanics

Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.

💡 Security Header Best Practices

HTTP security headers provide defense-in-depth with minimal implementation effort. Key headers include Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy, each addressing specific attack vectors.

🔍 Check Any IP Address

Share this report: