ABUSE.MOM
THREAT REPORT

IP Threat Report
160.187.211.243

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-26 01:42:57
First seen: 2026-07-06 06:08:45
Last seen: 2026-07-12 00:42:54
60

⛔ Verdict: BLOCK

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

DANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
160.187.211.243
Type
Residential
Country
🇲🇾 MY
City
Iskandar Puteri
ISP
Advin Services LLC
Organization
Advin Services LLC
Autonomous System
AS206216 Advin Services LLC
Hit Count
412
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 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-07-06 06:08:45
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 1 (+10), Danger strong hits: 1 (+25), UA changed (+25)
2026-07-12 00:42:54
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

Advin Services LLC
AS206216 · 🇲🇾 MY
06

Recommendations

Actions taken & recommended

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

🤖 Bot Detection

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

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

160.187.211.243 has been assigned a threat score of 60/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

160.187.211.243 is registered in Iskandar Puteri, MY, operating on the network of Advin Services LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 412 malicious requests from this address across a 5-day span, reflecting a sustained attack cadence of ~82.4 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇲🇾 Top threats from MY

View all →

🏢 Same network: AS206216

207.241.172.220 (105)212.193.3.111 (70)212.193.3.245 (60)View all →
12

Security Intelligence

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

🔍 Check Any IP Address

Share this report: