werasign.blogg.se

Nordvpn safe
Nordvpn safe










nordvpn safe

The 8chan discussion started on 5-3-2018, yes, but that's the US month-day-year format (3rd May), not European day-month-year (5th March), as NordVPN initially believed. That's interesting, but there's some confusion over times. Later our configuration was changed, so the config file would have looked differently.' The exposed configuration file indicated the attack happened on the same day, the company went on: 'March 5th was the last day when such configuration file existed. NordVPN initially told us: 'We believe that the discussion on 8chan was the cause for someone to start looking for vulnerabilities of different VPN service providers, and that discussion started on March 5th.' When did the hack occur, then? That's where the picture gets murky. NordVPN's details didn't include any dating information. That's either a very speedy hack, or the user already knew the vulnerability for each provider. That suggests the user hadn't just found these somewhere, or got them from someone else he saw the thread and grabbed live server information almost immediately. Scanning the text, we noticed the VikingVPN (opens in new tab) and TorGuard (opens in new tab) links appeared to show session connection times and some file information from Thursday May 3rd, the day the 8chan discussion began. Mullvad and cryptostorm got an approving 'good choice!', but NordVPN, TorGuard and VikingVPN got a 'lol, no', with links to evidence showing hacked server details from each provider: configuration files, private keys, basic session details and more. On May 3rd, 2018, a user on the 8chan message board started a discussion (opens in new tab) asking for VPN recommendations, and other users began adding their favorites: NordVPN, Mullvad, TorGuard, VikingVPN, cryptostorm and more.Īt 20:46, another user made a post commenting on these suggestions.












Nordvpn safe