IP Threat Report
182.95.52.122
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Burst: 5 req / 2s | Abnormally fast request rate — automated scanning | +35 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 182.95.52.122 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 182.95.52.122 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🌊 Traffic Flood Defense
IP 182.95.52.122 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 23 | Telnet | Critical | Telnet — unencrypted remote access, extremely dangerous if exposed |
| 53 | DNS | Low | DNS server — potential for DNS amplification attacks |
| 1701 | Unknown | Low | Service on port 1701 |
| 1883 | Unknown | Low | Service on port 1883 |
⚠️ Network scanning reveals 1 dangerous service exposed on 182.95.52.122. Telnet (23) transmits credentials in plaintext — likely a compromised IoT device. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2023-51767 | NVD → |
| CVE-2025-26465 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2021-41039 | NVD → |
| CVE-2023-0809 | NVD → |
| CVE-2023-28366 | NVD → |
| CVE-2008-3844 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2021-34431 | NVD → |
| CVE-2024-8376 | NVD → |
| CVE-2023-51384 | NVD → |
| CVE-2024-10525 | NVD → |
| CVE-2023-28531 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2021-34432 | NVD → |
| CVE-2023-3592 | NVD → |
| CVE-2024-6387 | NVD → |
🔴 Security scanning identified 19 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
182.95.52.122 has been assigned a threat score of 60/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.
The following attack categories were identified:
📊 Threat Analysis
Our monitoring infrastructure has identified 182.95.52.122, geolocated to New Delhi, India, operating on the network of Genpact India 4th Floor, as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 126 malicious IPs originating from India, positioning it as a significant contributor to global threat activity. 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.
Related Threats
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.
💡 Threat Intelligence Sharing Frameworks
Standards like STIX/TAXII, MISP, and OpenIOC enable automated sharing of threat intelligence between organizations. Collective defense through shared indicators, tactics, and procedures strengthens the entire security community against common threats.