Main navigation

Error message

Warning: Undefined array key 0 in amp_entity_view_alter() (line 156 of modules/contrib/amp/amp.module).
amp_entity_view_alter(Array, Object, Object) (Line: 545)
Drupal\Core\Extension\ModuleHandler->alter('node_view', Array, Object, Object) (Line: 304)
Drupal\Core\Entity\EntityViewBuilder->buildMultiple(Array) (Line: 238)
Drupal\Core\Entity\EntityViewBuilder->build(Array)
call_user_func_array(Array, Array) (Line: 111)
Drupal\Core\Render\Renderer->doTrustedCallback(Array, Array, 'Render #pre_render callbacks must be methods of a class that implements \Drupal\Core\Security\TrustedCallbackInterface or be an anonymous function. The callback was %s. See https://www.drupal.org/node/2966725', 'exception', 'Drupal\Core\Render\Element\RenderCallbackInterface') (Line: 788)
Drupal\Core\Render\Renderer->doCallback('#pre_render', Array, Array) (Line: 377)
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: 18)

Cryptopia Hacker’s Second Coming: Another $3.2 Mln in Crypto Gone As Users Kept Depositing Crypto

Advertisement
Wed, 30/01/2019 - 10:08
Cryptopia Hacker’s Second Coming: Another $3.2 Mln in Crypto Gone As Users Kept Depositing Crypto
Cover image via U.Today
Read U.TODAY on
Google News
Advertisement

Two weeks ago, U.Today reported about the hack of the New Zealand-based Cryptopia exchange. Back then, the platform’s team stated that the hacker had stolen around 13,400 ETH (about $2.44 mln) and nearly 50 mln CENNZ tokens (around $1.18 mln).

The tip of the iceberg

However, the DLT research company Elementus has figured out two weeks later that the real amount of the crypto taken away was much bigger – $16 mln. Elementus also warned that a lot of the exchange’s hot crypto addresses were still vulnerable to hacking.

Advertisement

The CEO of Elementus, Max Galka, mentioned that more than 5,000 Cryptopia wallets are still in danger and could be ‘visited’ by hackers again. Users of the exchange, who were probably unaware of the hack, continued putting funds into those wallets.

Related

The return of the thief

On Monday, Jan. 29, Elementus tracked several other withdrawals in ETH coins. The amount totalled nearly 31,000 ETH, which is around $3.2 mln.

First, the agency thought that it could be Cryptopia itself, taking its funds to a secure cold wallet. However, later it turned out that the address to which the transaction was made was the same as the one that accepted the stolen funds during the first attack.

The curious fact remains – investors kept topping up their Cryptopia wallets as the hacker was sucking ETH from the exchange, despite the loud news reports of the previous attack.

The head of Elementus assumed that these tokens were being sent to the exchange from miners through a ‘direct deposit’ automatically.

Related articles

Advertisement
TopCryptoNewsinYourMailbox
TopCryptoNewsinYourMailbox
Advertisement
Advertisement

Recommended articles

Latest Press Releases

Our social media
There's a lot to see there, too

Popular articles

Advertisement
AD