Warning: Undefined array key 1 in Drupal\cryptocompare\TwigExtension\RemoveSpace::getcard() (line 2999 of modules/custom/cryptocompare/src/TwigExtension/RemoveSpace.php). Drupal\cryptocompare\TwigExtension\RemoveSpace::getcard('Cryptocurrency derivatives BitMEX has swiftly addressed all the FUD surrounding the alleged "hack" that send shockwaves across the crypto community a few hours ago. The company claims that its Twitter account was targeted by "trolls" while reassuring users that all their funds are safe.
<blockquote class="twitter-tweet">
We would like to reassure our users that while the trolls may target our Twitter account, you may rest assured that all funds are safe.
— BitMEX (@BitMEXdotcom) <a rel="nofollow" target="_blank" href="https://twitter.com/BitMEXdotcom/status/1190267001714835456?ref_src=twsrc%5Etfw">November 1, 2019</a></blockquote>
Earlier on Friday, an accident happened on the BitMEX crypto exchange when thousands of it users had their <a href="https://u.today/crypto-community-responds-to-bitmex-leak-cz-urges-bitmex-users-to-change-their-binance-emails">email addresses leaked</a>.
BitMEX responded quickly, saying that they were working on the issue.
Binance’s CZ tweeted that all users who trade both on BitMEX and Binance should change their email addresses asap to prevent any troubles with their accounts on Binance.
Ads
Ads
<a rel="nofollow" target="_blank" href="#">card</a>
Binance provided a step-by-step guide for that. Other members of the community began offering advice on not using SMS 2FA and saying that the victims of the leak should change their passwords immediately to prevent hackers from stepping in.
Later, BitMEX tweeted that it had been hacked. However, a few minutes later, the tweet was removed.
Image by Twitter') (Line: 1031)
Drupal\cryptocompare\TwigExtension\RemoveSpace->formatbody(Array) (Line: 54)
__TwigTemplate_75845256f703f5319a38e035b4af7dd9->doDisplay(Array, Array) (Line: 394)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 367)
Twig\Template->display(Array) (Line: 379)
Twig\Template->render(Array, Array) (Line: 40)
Twig\TemplateWrapper->render(Array) (Line: 53)
twig_render_template('themes/cryptod/templates/field--body.html.twig', Array) (Line: 372)
Drupal\Core\Theme\ThemeManager->render('field', Array) (Line: 436)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array) (Line: 474)
Drupal\Core\Template\TwigExtension->escapeFilter(Object, Array, 'html', NULL, 1) (Line: 628)
__TwigTemplate_625426e732c5f7a66fde6d628d98a6b2->doDisplay(Array, Array) (Line: 394)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 367)
Twig\Template->display(Array) (Line: 52)
__TwigTemplate_e934e56c1e459c359b150360c7169113->doDisplay(Array, Array) (Line: 394)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 367)
Twig\Template->display(Array) (Line: 379)
Twig\Template->render(Array, Array) (Line: 40)
Twig\TemplateWrapper->render(Array) (Line: 53)
twig_render_template('themes/cryptod/templates/node.html.twig', Array) (Line: 372)
Drupal\Core\Theme\ThemeManager->render('node', Array) (Line: 436)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array, ) (Line: 238)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 583)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 239)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 128)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 187)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 191)
Drupal\page_cache\StackMiddleware\PageCache->fetch(Object, 1, 1) (Line: 128)
Drupal\page_cache\StackMiddleware\PageCache->lookup(Object, 1, 1) (Line: 82)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 704)
Drupal\Core\DrupalKernel->handle(Object) (Line: 17)
Warning: Undefined array key 1 in Drupal\cryptocompare\TwigExtension\RemoveSpace::getcard() (line 3002 of modules/custom/cryptocompare/src/TwigExtension/RemoveSpace.php). Drupal\cryptocompare\TwigExtension\RemoveSpace::getcard('Cryptocurrency derivatives BitMEX has swiftly addressed all the FUD surrounding the alleged "hack" that send shockwaves across the crypto community a few hours ago. The company claims that its Twitter account was targeted by "trolls" while reassuring users that all their funds are safe.
<blockquote class="twitter-tweet">
We would like to reassure our users that while the trolls may target our Twitter account, you may rest assured that all funds are safe.
— BitMEX (@BitMEXdotcom) <a rel="nofollow" target="_blank" href="https://twitter.com/BitMEXdotcom/status/1190267001714835456?ref_src=twsrc%5Etfw">November 1, 2019</a></blockquote>
Earlier on Friday, an accident happened on the BitMEX crypto exchange when thousands of it users had their <a href="https://u.today/crypto-community-responds-to-bitmex-leak-cz-urges-bitmex-users-to-change-their-binance-emails">email addresses leaked</a>.
BitMEX responded quickly, saying that they were working on the issue.
Binance’s CZ tweeted that all users who trade both on BitMEX and Binance should change their email addresses asap to prevent any troubles with their accounts on Binance.
Ads
Ads
<a rel="nofollow" target="_blank" href="#">card</a>
Binance provided a step-by-step guide for that. Other members of the community began offering advice on not using SMS 2FA and saying that the victims of the leak should change their passwords immediately to prevent hackers from stepping in.
Later, BitMEX tweeted that it had been hacked. However, a few minutes later, the tweet was removed.
Image by Twitter') (Line: 1031)
Drupal\cryptocompare\TwigExtension\RemoveSpace->formatbody(Array) (Line: 54)
__TwigTemplate_75845256f703f5319a38e035b4af7dd9->doDisplay(Array, Array) (Line: 394)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 367)
Twig\Template->display(Array) (Line: 379)
Twig\Template->render(Array, Array) (Line: 40)
Twig\TemplateWrapper->render(Array) (Line: 53)
twig_render_template('themes/cryptod/templates/field--body.html.twig', Array) (Line: 372)
Drupal\Core\Theme\ThemeManager->render('field', Array) (Line: 436)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array) (Line: 474)
Drupal\Core\Template\TwigExtension->escapeFilter(Object, Array, 'html', NULL, 1) (Line: 628)
__TwigTemplate_625426e732c5f7a66fde6d628d98a6b2->doDisplay(Array, Array) (Line: 394)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 367)
Twig\Template->display(Array) (Line: 52)
__TwigTemplate_e934e56c1e459c359b150360c7169113->doDisplay(Array, Array) (Line: 394)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 367)
Twig\Template->display(Array) (Line: 379)
Twig\Template->render(Array, Array) (Line: 40)
Twig\TemplateWrapper->render(Array) (Line: 53)
twig_render_template('themes/cryptod/templates/node.html.twig', Array) (Line: 372)
Drupal\Core\Theme\ThemeManager->render('node', Array) (Line: 436)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array, ) (Line: 238)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 583)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 239)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 128)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 187)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 191)
Drupal\page_cache\StackMiddleware\PageCache->fetch(Object, 1, 1) (Line: 128)
Drupal\page_cache\StackMiddleware\PageCache->lookup(Object, 1, 1) (Line: 82)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 704)
Drupal\Core\DrupalKernel->handle(Object) (Line: 17)
Alex Dovbnya
Denys Serhiichuk