ABUSE.MOM
THREAT REPORT

IP Threat Report
161.35.168.32

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 08:08:26
First seen: 2026-10-21 18:02:56
Last seen: 2026-10-25 04:07:49
155

⛔ Verdict: BLOCK

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

DANGER_PATHUA_SUS
01

Geolocation & Classification

IP Address
161.35.168.32
Type
Hosting
Country
🇬🇧 United Kingdom
City
Slough
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
58
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 4Medium-risk: admin panels, config files+40
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 155
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-10-21 18:02:56
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 4 (+40), Danger strong hits: 4 (+100), UA suspicious (+15)
2026-10-25 04:07:49
Last malicious request observed
Total score reached: 155/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇬🇧 United Kingdom

We have detected 4069 malicious IPs from this autonomous system.

View all IPs from AS14061 →
06

Recommendations

Actions taken & recommended

  • IP 161.35.168.32 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.168.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

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

07

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

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

10

Threat Analysis

161.35.168.32 has been assigned a threat score of 155/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

Network traffic from 161.35.168.32, located in Slough, United Kingdom, operating on the network of DigitalOcean, LLC, has been classified as malicious by our automated threat scoring engine. During its 3-day observation window, we recorded 58 hostile requests from this IP — roughly 19.3 per day on average. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. United Kingdom currently accounts for 3,199 blocked IPs in our database, making it a major source of malicious traffic. With a threat score of 155/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 Kingdom

45.86.203.126 (350)45.138.12.41 (350)91.230.225.114 (350)45.138.12.46 (350)185.192.71.72 (350)View all →

🏢 Same network: AS14061

168.144.130.251 (280)142.93.195.73 (275)152.42.236.252 (273)165.22.77.209 (273)46.101.208.236 (273)View all →
12

Security Intelligence

💡 SQL Injection Campaigns

SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.

💡 Responsible Disclosure Ethics

Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.

🔍 Check Any IP Address

Share this report: