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)
Hackers Compromise BitPay’s Wallet, Adding Malware to the Code
BitPay has announced through GitHub that some hacker modified part of its Copay wallet’s software to upload some malicious code into it.
BitPay’s app remains secure
The hacker installed the virus on the wallet’s modifications 5.0.2 up to 5.1.0 of Copay and BitPay’s crypto storage apps. Experts believe this malicious code can be utilized for stealing private keys in order to get hold of customers’ BTC and BCH coins.
BitPay reps assure that the company’s app proved to be not vulnerable to the hackers’ attempts to compromise it. But currently they are busy researching if any damage has been done to the users of Copay’s platform.
Yuri MolchanSecure update already released
The company urges its customers not to switch on their Copay wallets if it is versions 5.0.2 – 5.1.0 that they use. BitPay and Copay together have already managed to create and release an improved wallet – the 5.2.0 version, which does not contain any malicious codes and can be used by all customers of both BitPay and Copay. The companies assure that the updated version of the wallet will appear in online stores instantly.
BitPay has warned their clients that since keys on the infected wallets were probably copied, they had better transfer their crypto to the new version of the Copay wallet as soon as possible. The company also noted that users should not import their seed phrases made up of 12 words, since they too can be compromised and serve as a way to restore lost crypto.
The recommended way to transfer their coins from old vaults to the new ones is the Send Max feature, suggests BitPay.
The main suspect
It is believed that the trouble was initiated by a fake developer nicknamed Right9ctrl. He took over maintaining the NodeJS library from the guy who created it but could no longer devote time to work on the library. The latter reportedly took place a quarter of a year ago. Back then, the fake developer got access to the library and infected it with malware.
Related articles
Tomiwabold Olajide
Gamza Khanzadaev
Vladislav Sopov
Dan Burgin