ABUSE.MOM
THREAT REPORT

IP Threat Report
195.19.50.114

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-06-29 12:56:50
First seen: 2026-06-21 05:06:24
Last seen: 2026-06-27 20:14:17
95

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

IP Address
195.19.50.114
Type
Unknown
Country
🇷🇺 Russia
City
Moscow
ISP
ZAO GTNT
Organization
ZAO GTNT
Autonomous System
Unknown
Hit Count
972
02

Detection Signatures

SignatureDescriptionPointsSeverity
Directory ScanBehavioral anomaly detected by automated analysis+0
Σ = 0
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-06-21 05:06:24
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Directory Scan
2026-06-27 20:14:17
Last malicious request observed
Total score reached: 95/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 195.19.50.114 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 195.19.50.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

⚙️ Defensive Recommendations

Block 195.19.50.114 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

07

Neighbors in 195.19.50.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org

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

10

Threat Analysis

195.19.50.114 has been assigned a threat score of 95/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

📊 Threat Analysis

Threat intelligence analysis has linked 195.19.50.114 to malicious activity originating from Moscow, Russia, operating on the network of ZAO GTNT. The address has been under observation since its initial detection. During its 6-day observation window, we recorded 972 hostile requests from this IP — roughly 162 per day on average. Russia currently accounts for 104 blocked IPs in our database, making it a significant source of malicious traffic. At 95/100, this is an extremely high-risk address. All traffic should be considered hostile.

11

Related Threats

🇷🇺 Top threats from Russia

157.22.102.172 (313)178.130.54.159 (288)185.103.167.63 (265)72.56.191.6 (265)95.182.125.201 (265)View all →
12

Security Intelligence

💡 Cloud Infrastructure Abuse

Cloud platforms provide attackers with elastic, disposable infrastructure. Free tier accounts, stolen credit cards, and compromised cloud credentials enable rapid deployment of attack infrastructure that can scale to millions of requests and disappear within hours.

💡 WebSocket Security Considerations

WebSocket connections bypass traditional HTTP security controls, creating opportunities for cross-site WebSocket hijacking, denial of service, and data injection. Proper origin validation, authentication, and message rate limiting are essential for secure WebSocket implementations.

🔍 Check Any IP Address

Share this report: