IP Threat Report
82.180.144.237
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| POST requests present | Behavioral anomaly detected by automated analysis | +8 |
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 82.180.144.237 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
⚙️ General Security
Add 82.180.144.237 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 21 | FTP | Medium | File Transfer Protocol — often targeted for anonymous login attacks |
| 25 | SMTP | Medium | SMTP mail server — can be abused for spam relay |
| 53 | DNS | Low | DNS server — potential for DNS amplification attacks |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 110 | POP3 | Low | Service on port 110 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 465 | Unknown | Low | Service on port 465 |
| 587 | Unknown | Low | Service on port 587 |
| 2030 | Unknown | Low | Service on port 2030 |
| 2031 | Unknown | Low | Service on port 2031 |
| 2082 | Unknown | Low | Service on port 2082 |
| 2083 | Unknown | Low | Service on port 2083 |
| 2087 | Unknown | Low | Service on port 2087 |
⚠️ 1 high-risk port detected on 82.180.144.237. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2024-25117 | NVD → |
| CVE-2019-9511 | NVD → |
| CVE-2021-3618 | NVD → |
| CVE-2017-8923 | NVD → |
| CVE-2023-44487 | NVD → |
| CVE-2007-3205 | NVD → |
| CVE-2022-37454 | NVD → |
| CVE-2019-9513 | NVD → |
| CVE-2019-20372 | NVD → |
| CVE-2022-31628 | NVD → |
| CVE-2018-16845 | NVD → |
| CVE-2025-23419 | NVD → |
| CVE-2022-4900 | NVD → |
| CVE-2019-9516 | NVD → |
| CVE-2022-31629 | NVD → |
| CVE-2013-2220 | NVD → |
| CVE-2020-7070 | NVD → |
| CVE-2024-3566 | NVD → |
| CVE-2021-23017 | NVD → |
| CVE-2020-7069 | NVD → |
| CVE-2019-11048 | NVD → |
| CVE-2020-7068 | NVD → |
🔴 Security scanning identified 22 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
82.180.144.237 has been assigned a threat score of 68/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.
📊 Threat Analysis
Threat intelligence analysis has linked 82.180.144.237 to malicious activity originating from Navi Mumbai, India, operating on the network of Contabo Asia Private Limited. The address has been under observation since its initial detection. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 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. India currently accounts for 18 blocked IPs in our database, making it a notable source of malicious traffic. The score of 68/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.
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.
Related Threats
🇮🇳 Top threats from India
62.72.43.237 (305)217.216.78.172 (230)217.216.79.192 (230)217.216.79.203 (230)217.216.58.209 (195)View all →🏢 Same network: AS141995
62.72.43.237 (305)194.233.69.211 (273)62.146.239.75 (255)46.250.229.47 (245)217.216.32.203 (230)View all →Security Intelligence
💡 Brute Force Attack Mechanics
Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.
💡 VPN Exit Node Reputation
VPN exit nodes aggregate traffic from many users, creating mixed reputation profiles. While legitimate users seek privacy, attackers exploit VPN services to anonymize malicious activity, making IP-based blocking of VPN nodes a complex policy decision.