IP Threat Report
82.64.128.248
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
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.64.128.248 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
🔎 Directory Scan Defense
IP 82.64.128.248 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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 |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
⚠️ Network scanning reveals 1 dangerous service exposed on 82.64.128.248. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2019-12815 | NVD → |
| CVE-2018-1301 | NVD → |
| CVE-2017-3169 | NVD → |
| CVE-2016-8612 | NVD → |
| CVE-2017-9798 | NVD → |
| CVE-2024-24795 | NVD → |
| CVE-2006-20001 | NVD → |
| CVE-2021-40438 | NVD → |
| CVE-2024-38475 | NVD → |
| CVE-2024-38473 | NVD → |
| CVE-2014-3583 | NVD → |
| CVE-2022-30556 | NVD → |
| CVE-2022-36760 | NVD → |
| CVE-2017-7679 | NVD → |
| CVE-2024-47252 | NVD → |
| CVE-2024-40898 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2017-9788 | NVD → |
| CVE-2024-39573 | NVD → |
| CVE-2016-4975 | NVD → |
| CVE-2021-34798 | NVD → |
| CVE-2018-1312 | NVD → |
| CVE-2024-38476 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2023-38709 | NVD → |
🔴 Security scanning identified 108 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.64.128.248 has been assigned a threat score of 85/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:
📊 Threat Analysis
Our monitoring infrastructure has identified 82.64.128.248, geolocated to Paris, France, operating on the network of ProXad network / Free SA, as a source of suspicious network activity. Over a period of 20 days, this IP generated 13 malicious requests, averaging approximately 0.7 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 131 flagged addresses, France represents a significant presence in our threat database. The score of 85/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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
💡 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.
💡 Patch Management Urgency
The window between vulnerability disclosure and exploitation continues to shrink. Critical CVEs are now exploited within hours of publication. Automated patch management, virtual patching through WAFs, and rapid deployment pipelines are essential for timely remediation.