Bad Packets Profile picture
May 4, 2018 10 tweets 7 min read Twitter logo Read on Twitter
#Coinhive found on the website of the San Diego Zoo (@sandiegozoo) in the latest high-profile case of #cryptojacking.
How did it get there? @ninoseki shares the details here:
As for why did it happen, we can clearly see the site is running an outdated (vulnerable) version of #Drupal.
I've contacted @sandiegozoo and advised them to remove the code ASAP and update to the latest Drupal version.

Coinhive is injected via obfuscated code found in…
So who owns

WHOIS records indicate it belongs to "X XYZ" who lives on "joker joker" street in China.
While the clearly fake WHOIS data may seem like a dead end, the same email address ( was used to register five other domains. It's likely you'd find malicious activity tied to these as well. One of the domains references less-fake information.
For now we'll stick with the facts at hand:
@sandiegozoo's website compromised to run #Coinhive
Domain used to inject the malware:
Current hosting provider: @QuadraNet
Domain registrar: @Namecheap
Looking at the historical DNS records on @securitytrails we find was recently involved in Monero (XMR) mining operations. So it seems fitting to continue the trend with today's cryptojacking incident using #Coinhive.
#Coinhive has been removed from the @sandiegozoo website. @urlscanio confirms the site is clean now as well.
Please unroll.

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Bad Packets

Bad Packets Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @bad_packets

Aug 30, 2018
Tor Browser not required for this shop.
Read 6 tweets
May 2, 2018
If you run a @Google phishing site and use @letsencrypt, make sure to use Certbot to keep the SSL cert updated automatically.

Looking good here!
Oops, forgot to add the SAN!
Read 14 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!


0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy


3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!