consumers into handing over passwords and credit card details by taking advantage of the flood of emails being sent outAttack.Phishingahead of new European privacy legislation . The European Union 's new General Data Protection Regulation ( GDPR ) come into force on 25 May and the policy is designed to give consumers more control over their online data . As a result , in the run-up to it , organisations are sending outAttack.Phishingmessages to customers to gain their consent for remaining on their mailing lists . With so many of these messages being sent outAttack.Phishing, it was perhaps only a matter of time before opportunistic cybercriminals looked to take advantage of the deluge of messages about GDPR and privacy policies arriving in people 's inboxes . A GDPR-related phishing scamAttack.Phishinguncovered by researchers at cyber security firm Redscan is doing just this in an effort to steal data with emails claiming to beAttack.Phishingfrom Airbnb . The attackers appear to beAttack.Phishingtargeting business email addresses , which suggests the messages are sentAttack.Phishingto emails scraped from the web . The phishing message addresses the user as an Airbnb host and claimsAttack.Phishingthey 're not able to accept new bookings or sendAttack.Phishingmessages to prospective guests until a new privacy policy is accepted . `` This update is mandatory because of the new changes in the EU Digital privacy legislation that acts upon United States based companies , like Airbnb in order to protect European citizens and companies , '' the message says , and the recipient is urgedAttack.Phishingto click a link to accept the new privacy policy . Those who click the link are asked to enter their personal information , including account credentials and payment card information . If the user enters these , they 're handing the data straight into the hands of criminals who can use it for theft , identity fraud , selling on the dark web and more . `` The irony wo n't be lost on anyone that cybercriminals are exploiting the arrival of new data protection regulations to stealAttack.Databreachpeople 's data , '' said Mark Nicholls , Director of Cyber Security at Redscan . `` Scammers know that people are expecting exactly these kinds of emails this month and that they are required to take action , whether that 's clicking a link or divulging personal data . It 's a textbook phishing campaignAttack.Phishingin terms of opportunistic timing and having a believable call to action '' . Airbnb is sending messages to users about GDPR , but the messages contain far more detail and do n't ask the users to enter any credentials , merely agree to the new Terms of Service . While the phishing messages might look legitimate at first glance , it 's worth noting they do n't use the right domain - the fake messages come fromAttack.Phishing' @ mail.airbnb.work ' as opposed to ' @ airbnb.com ' . Redscan has warned that attackers are likely to use GDPR as baitAttack.Phishingfor other phishing scamsAttack.Phishing, with messages claiming to beAttack.Phishingfrom other well-known companies . `` As we get closer to the GDPR implementation deadline , I think we can expect to see a lot a lot more of these types of phishing scamsAttack.Phishingover the next few weeks , that 's for sure , '' said Nicholls , who warned attackers could attempt to use the ploy to deliver malware in future . `` In the case of the Airbnb scam email , hackers were attempting to harvestAttack.Databreachcredentials . Attack vectors do vary however and it 's possible that other attacks may attempt to infect hosts with keyloggers or ransomware , for example . '' he said . Airbnb said those behind the attacks have n't accessedAttack.Databreachuser details in order to sendAttack.Phishingemails and that users who receiveAttack.Phishinga suspicious message claiming to beAttack.Phishingfrom Airbnb should send it to their safety team . `` These emails are a brazen attempt at using our trusted brand to try and stealAttack.Databreachuser 's details , and have nothing to do with Airbnb . We 'd encourage anyone who has receivedAttack.Phishinga suspicious looking email to report it to our Trust and Safety team on report.phishing @ airbnb.com , who will fully investigate , '' an Airbnb spokesperson told ZDNet . Airbnb also provided information on how to spot a fake email to help users to determine if a message is genuine or not .
A hacker that goes by the nickname of Cipher0007 has hacked the Sanctuary Dark Web marketplace . The hacker announced the breach a few hours ago and also posted proof of his intrusion . According to Cipher0007 , the hack took place after he foundVulnerability-related.DiscoverVulnerabilityan SQL injection flaw in the market 's database . The hacker claimsVulnerability-related.DiscoverVulnerabilityhe used the SQL injection flaw to upload a shell on the market 's server . He then used this backdoor to accessAttack.Databreachvarious parts of the backend and dumpedAttack.Databreachthe private key used to generate the market 's .onion URL . Cipher0007 also says he used the market 's phpMyAdmin installation to dumpAttack.Databreachdetails on the database configuration and other login information . At the time of writing , the market 's phpMyAdmin login page was still exposed to external connections . To prove his claims , the hacker posted online a screengrab while uploading the shell to the Sanctuary market 's server , the market 's 1024 bit RSA private key , and the market 's root account database login information . The Sanctuary market is a small Dark Web market , and one of the few places where digital products such as data dumps , malware , and others , are far more prevalent than drugs and weapons . The admin of the Sanctuary market did not respond to a request for comment from Bleeping Computer in time for this article 's publication . Cipher0007 has a reputation in the hacking underground already . In January , the hacker collected an unspecified Bitcoin reward for reportingVulnerability-related.DiscoverVulnerabilitya bug to the AlphaBay staff that would have allowed an attacker access to over 218,000 private messages . AlphaBay is today 's biggest Dark Web market , and access to those PMs would have allowed an attacker insight into the operations of many sellers and vendors .
A case involving software vulnerabilities in medical electronics revealsVulnerability-related.DiscoverVulnerabilitythe inability for both the health care sector and federal regulators to swiftly address cybersecurity problems . This past fall , an investment firm rattled the health care industry with unsubstantiated claimsVulnerability-related.DiscoverVulnerabilityof multiple software vulnerabilities in internet-connected pacemakers and cardiac defibrillators . But it took federal authorities who regulate medical devices four months to acknowledgeVulnerability-related.DiscoverVulnerabilityonly one of the alleged defects , and for the company , St. Jude Medical , to patchVulnerability-related.PatchVulnerabilityit . The delayed response to a problem that could potentially put patients at risk raises many questions about why it took so long for the government to act , and what it will take for the health care industry to respond more swiftly to bugs in medical equipment increasingly connected to the internet . `` Software is never perfect and all systems still will have these flaws , '' says Joshua Corman , director of the Cyber Statecraft Initiative at the Atlantic Council and an expert on medical device security . `` The question is how gracefully and collaboratively and quickly and safely can we respond to these flaws . '' In this particular case , legal action as well as the unusual way the St. Jude vulnerabilities came to light may have stifled the response . A cybersecurity firm called MedSec initially discoveredVulnerability-related.DiscoverVulnerabilitythe problems in the St. Jude devices and tipped off the activist investment firm Muddy Waters , which publicizedVulnerability-related.DiscoverVulnerabilitythe flaws and advised clients to bet against the health care firm 's stock . As a result , St. Jude lodged a defamation lawsuit against MedSec and Muddy Waters , denying many of the alleged glitches in its pacemaker and implantable defibrillator systems . `` In theory , most disclosures now should take about 60 days to get to some clarity or resolution , '' said Corman . `` In part , because of the contentious nature and the lawyers involved in this particular one , it took about five months . '' Last week , the Food and Drug Administration along with the Department of Homeland Security confirmedVulnerability-related.DiscoverVulnerabilityat least some of MedSec's findings and reportedVulnerability-related.DiscoverVulnerabilitya flaw in the St. Jude @ Merlin transmitter , an at-home computer that sends data from cardiac implants to the patient 's medical team . The flaw could have allowed malicious hackers to remotely exhaust an implant 's battery power or potentially harm the patient . St. Jude spokeswoman Candace Steele Flippin said in an emailed statement that following the release of Muddy Waters ' claimsVulnerability-related.DiscoverVulnerabilityin August , the device manufacturer `` carefully reviewed the claimsVulnerability-related.DiscoverVulnerabilityin these reports along with our existing plans for our cyber ecosystem , '' evaluated them with FDA , DHS , and outside security researchers , and then identified the improvements announced on Jan. 9 and noted further enhancements `` we will be making in the coming months . '' But Muddy Waters said the problems may take as long as two years to fix . Carson Block , the firm 's founder , said this week the root causes of the vulnerabilities demand a change to firmware inside the St. Jude implants themselves . The firm said in a statement , `` these issues have just been givenVulnerability-related.PatchVulnerabilitya quick fix by St. Jude with the government 's blessing and cardiologists should go with other pacemaker manufacturers since they are much better on cybersecurity . '' It 's important to note that all the players in this medical legal drama , as well as the Veterans Affairs Department , which buys St. Jude devices , say there have been no reports of patient harm related to the cybersecurity vulnerabilities reported late August . In fact , the VA in recent months has continued paying for operations involving St. Jude devices , according to contract documents . Ever since the US government and St. Jude confirmedVulnerability-related.DiscoverVulnerabilitythe one flaw , the VA has been `` taking steps to be sure all our patients and providers are aware of this issue and take appropriate actions to be sure that all our patients get the update for their monitor , ” said Merritt Raitt , acting director of the VA National Cardiac Device Surveillance Program . The controversy could have been partly avoided , perhaps , if St. Jude and MedSec had followed new federal regulations for medical device security that encourage manufacturers to be more proactive about addressing potential vulnerabilities . A week before federal regulators publicized the one St. Jude glitch on Jan. 9 , they announced the completion of a 2016 draft policy that might have yielded multiple fixes in two months without anyone resorting to public shaming or legal action . On Jan. 4 , DHS circulated the final Food and Drug Administration ( FDA ) cybersecurity guidelines for monitoring networked medical devices on the market that threaten manufacturers with penalties such as a recall unless they cooperate with bug hunters to patchVulnerability-related.PatchVulnerabilityvulnerabilities within 60 days . Corman recommends that providers , including VA , heed all the literature that 's been published on the St. Jude glitches , including a DHS technical advisory , FDA security communication , MedSec report , and guidance written by Bishop Fox , a cybersecurity consultancy Muddy Waters hired in response to the lawsuit . `` Just understand that the FDA and DHS do need to get the ground truth , that security researcher claims do need to be validated through the normal regulatory process , '' he says .
A miscreant using the handle @ cyberzeist claimsVulnerability-related.DiscoverVulnerabilityto have infiltrated Plone CMS used by FBI.gov , using a zero day flaw allegedly for sale on an unnamed dark web site . The Register has contacted the FBI to confirm the allegations . The agency was not immediately available for comment – although a staffer said they were aware of the alleged break-in . Cyberzeist claims to have conducted the hack last month and has posted to Twitter what they claim are screen captures showing the FBI patchingVulnerability-related.PatchVulnerabilityagainst the vulnerability , which appeared to permit public access . The hacker dumpedAttack.Databreachthe 155 purported stolen credentials to online clipboard pastebin , claimingVulnerability-related.DiscoverVulnerabilitya vulnerability resides inVulnerability-related.DiscoverVulnerabilitya Plone Python module . Cyberzeist also claimed the FBI contacted the hacker requesting a copy of the stolen credentials , which they declined to provide . The hacker reckoned the CMS was hosted on a virtual machine running a custom FreeBSD . They said they will tweet the zero day flaw once it is no longer for sale .