ABUSE.MOM
THREAT REPORT

IP Threat Report
103.153.182.11

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:22:20
First seen: 2026-04-06 17:00:07
Last seen: 2026-04-29 06:00:05
320

⛔ Verdict: BLOCK

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

UA_CHANGEDBURSTMETHODBOT_UADANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
103.153.182.11
Type
Hosting
Country
🇺🇸 United States
City
Dallas
ISP
Harsh Jain
Organization
Unknown
Autonomous System
AS140947 SnTHostings
Hit Count
12
02

Detection Signatures

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

Network Provider

Harsh Jain
AS140947 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 103.153.182.11 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 103.153.182.11 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🌊 Flood / DDoS Mitigation

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

🔎 Directory Scan Defense

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

09

Blacklist Status (DNSBL)

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

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ 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

103.153.182.11 has been assigned a threat score of 320/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

User-Agent AnomalyRequest FloodingPath Enumeration

📊 Threat Analysis

Network traffic from 103.153.182.11, located in Dallas, United States, operating on the network of Harsh Jain, has been classified as malicious by our automated threat scoring engine. During its 22-day observation window, we recorded 12 hostile requests from this IP — roughly 0.5 per day on average. 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. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. With 222 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 320/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 States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS140947

103.153.183.126 (320)103.153.183.73 (298)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Botnet Command and Control Evolution

Botnet C2 infrastructure has evolved from centralized IRC channels to resilient peer-to-peer networks, domain generation algorithms, and blockchain-based communication. This evolution makes botnet takedowns increasingly difficult and expensive.

🔍 Check Any IP Address

Share this report: