ABUSE.MOM
THREAT REPORT

IP Threat Report
202.141.104.182

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 10:26:10
First seen: 2026-05-20 19:05:20
Last seen: 2026-05-24 10:19:47
78

⛔ Verdict: BLOCK

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

DANGER_PATHMETHODRATIO_404UA_CHANGED
01

Geolocation & Classification

IP Address
202.141.104.182
Type
Residential
Country
🇮🇳 India
City
Gurugram
ISP
NIXI
Organization
RailTel Corporation
Autonomous System
Unknown
Hit Count
396
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger medium hits: 2Medium-risk: admin panels, config files+20
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 78
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-05-20 19:05:20
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger medium hits: 2 (+20), POST seen (+8)
2026-05-24 10:19:47
Last malicious request observed
Total score reached: 78/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 202.141.104.182 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

Block scanning from 202.141.104.182: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 Bot Detection

Address UA spoofing from 202.141.104.182: 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
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
bl.spamcop.net
✓ Clean
cbl.abuseat.org

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

10

Threat Analysis

202.141.104.182 has been assigned a threat score of 78/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:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

The address 202.141.104.182 originates from Gurugram, India, operating on the network of NIXI. 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 396 flagged requests at a rate of ~132/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. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. A threat score of 78/100 places this IP in the high-risk category. Blocking at the firewall level is 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 India

144.16.219.228 (103)202.141.28.67 (103)202.141.38.234 (68)View all →
12

Security Intelligence

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

💡 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: