ABUSE.MOM
THREAT REPORT

IP Threat Report
161.35.135.215

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-08 17:43:31
First seen: 2026-08-06 03:59:02
Last seen: 2026-08-09 04:10:34
68

⛔ Verdict: BLOCK

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

BOT_UAMETHODREDIRECT_PROBE
01

Geolocation & Classification

IP Address
161.35.135.215
Type
Hosting
Country
🇺🇸 United States
City
Clifton
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
71
02

Detection Signatures

SignatureDescriptionPointsSeverity
POST seenBehavioral anomaly detected by automated analysis+8
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA bot: pythonKnown bot/crawler User-Agent detected+40
Σ = 68
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-06 03:59:02
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
POST seen (+8), Probe 302→404 (+20), UA bot: python (+40)
2026-08-09 04:10:34
Last malicious request observed
Total score reached: 68/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🤖 Bot Detection

Address UA spoofing from 161.35.135.215: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

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

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

10

Threat Analysis

161.35.135.215 has been assigned a threat score of 68/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

The address 161.35.135.215 originates from Clifton, United States, operating on the network of DigitalOcean, LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 3 days in our monitoring system, producing 71 flagged requests at a rate of ~23.7/day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 131 blocked IPs in our database, making it a significant source of malicious traffic. At 68/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

142.93.195.73 (275)152.42.236.252 (273)204.48.19.26 (268)157.230.45.147 (265)152.42.180.126 (263)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 Backup and Recovery Against Ransomware

Immutable, offline backups remain the most effective defense against ransomware. The 3-2-1 rule — three copies on two media types with one offsite — combined with regular recovery testing ensures business continuity after encryption attacks.

🔍 Check Any IP Address

Share this report: