ABUSE.MOM
THREAT REPORT

IP Threat Report
213.111.157.32

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:22:17
First seen: 2026-03-29 14:00:06
Last seen: 2026-04-03 00:00:08
293

⛔ Verdict: BLOCK

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

UA_CHANGEDDANGER_PATHRATIO_404BOT_UAMETHODBURST
01

Geolocation & Classification

IP Address
213.111.157.32
Type
Residential
Country
🇸🇬 Singapore
City
Singapore
ISP
Trunk-Networks
Organization
Unknown
Autonomous System
AS43180 Trunk Networks LTD
Hit Count
10
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 1Medium-risk: admin panels, config files+10
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 4Medium-risk: admin panels, config files+40
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
POST requests presentBehavioral anomaly detected by automated analysis+8
Danger strong hits: 23High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 6Medium-risk: admin panels, config files+60
Danger strong hits: 17High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 12Medium-risk: admin panels, config files+60
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 813
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-29 14:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Danger strong hits: 3 (+75), Danger medium hits: 1 (+10)
2026-04-03 00:00:08
Last malicious request observed
Total score reached: 293/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Trunk-Networks
AS43180 · 🇸🇬 Singapore
06

Recommendations

Actions taken & recommended

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

🤖 User-Agent Anomaly Defense

IP 213.111.157.32 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🔎 Directory Scan Defense

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

🌊 Flood / DDoS Mitigation

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

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (1)
PortServiceRiskDescription
22SSHLowSecure Shell — common brute force target for remote access
DETECTED TECHNOLOGIES
openbsd:openssh:9.2p1linux:linux_kerneldebian:debian_linux
Hostnames: dedicated.sollutium.com
PTR: dedicated.sollutium.com

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

213.111.157.32 has been assigned a threat score of 293/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 AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

213.111.157.32 is registered in Singapore, Singapore, operating on the network of Trunk-Networks. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 4 days, this IP generated 10 malicious requests, averaging approximately 2.5 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 208 flagged addresses, Singapore represents a significant presence in our threat database. With a threat score of 293/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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 Singapore

85.203.23.12 (340)85.203.23.31 (330)84.17.39.195 (325)192.166.246.30 (325)85.203.21.101 (320)View all →

🏢 Same network: AS43180

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.

💡 Race Condition Vulnerabilities

Race conditions occur when application behavior depends on the timing of concurrent operations. Attackers exploit these timing windows to bypass limits, duplicate transactions, or escalate privileges by sending carefully timed parallel requests.

🔍 Check Any IP Address

Share this report: