Severe Risk
IP 87.120.191.125 is a critical-risk address associated with 301 documented hacking attempts targeting automated honeypot sensors, with all reported activity concentrated in November 2025 and a 10/10 threat level indicating severe malicious intent despite a current activity frequency of zero.
The IP address 87.120.191.125 generated 301 total abuse reports, with 20 recent hacking-category incidents documented through automated honeypot sensors in November 2025, yielding a 75% confidence score in the assessment. The address routes through AS215925, operated by Vpsvault.host Ltd, with the network geolocated to the United States according to available data. Despite the substantial 301 total abuse reports accumulated, the current activity frequency registers at 0/10, suggesting a significant decline in recent hostile probing activity. The concentration of all reports within a single month and the exclusive use of honeypot detection mechanisms provides strong contextual evidence for sustained, targeted scanning behavior during the reporting period.
Hacking activity encompasses unauthorized intrusion attempts, vulnerability exploitation, and systematic probing for entry points into exposed network services. The 20 recent hacking-category reports from IP 87.120.191.125 indicate deliberate attempts to compromise systems rather than opportunistic scanning. While the current zero activity frequency suggests the address may be dormant or redirected, the historical volume of 301 reports and critical threat designation underscore that any exposed service encountering this traffic faces substantial risk of credential compromise, data exfiltration, or backdoor installation. Organizations with vulnerable SSH, RDP, or web-facing services remain at highest risk should activity resume.
Site operators should implement proactive defensive controls including network-level blocking or rate-limiting for the address, deployment of intrusion detection systems to alert on similar probing patterns, and enforcement of strong authentication requirements for all exposed services. Regular patching cycles, fail2ban deployment for SSH services, and monitoring for the described attack patterns will reduce the likelihood of successful exploitation even if activity resumes. Maintaining threat intelligence feeds and reviewing firewall logs for connection attempts matching the detected behavior will support ongoing situational awareness.
KR 
UA 
UZ 
RO 
CO 
CA