meta_pixel
Tapesearch Logo
Log in
CoinDesk Podcast Network

How Kraken Unmasked a North Korean Hacker

CoinDesk Podcast Network

CoinDesk

Cryptocurrencies, Cryptocurrency, Dlt, Tokenization, Coindesk, Distributed Ledger, Blockchain, Tech News, Business News, Ethereum, Bitcoin, News, Digitalassets, Daily News, Decentralization, Defi, Crypto, Business

4.8689 Ratings

🗓️ 2 May 2025

⏱️ 9 minutes

🧾️ Download transcript

Summary

Kraken's security team identified a North Korean hacker trying to infiltrate the company - how did they do it?

Kraken's security team recently identified a North Korean hacker who attempted to infiltrate the company by applying for a job at the crypto exchange. Kraken Chief Security Officer, Nick Percoco joins CoinDesk to discuss how it happened.

This content should not be construed or relied upon as investment advice. It is for entertainment and general information purposes.

-

This episode was hosted by Jennifer Sanasie.

See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Transcript

Click on a timestamp to play from that location

0:00.0

Krakken recently revealed an intelligence gathering operation that started as a routine hiring process.

0:06.6

During the operation, the crypto exchange recorded interviews and information as a suspect North Korean operative attempted to get a job in IT at the firm.

0:16.0

Crackin's chief security officer, Nick Perkoko, joins us now. Nick, welcome to CoinDesk.

0:22.1

Yeah, hey, thanks for having me.

0:28.9

All right. Crazy story. Let's start here. What tipped you off that you might be talking to a North Korean spy?

0:35.2

Yeah, so we have a lot of intelligence sources that flow into Cracken constantly, you know, through various industry groups, other forums that were part of. And,

0:39.3

you know, we had received a list of email addresses of known adversaries. Some were known as

0:46.7

potential North Koreans. And whenever we receive either email addresses or IP addresses or other

0:52.3

sort of identifiable information, we scrub our systems

0:55.3

to try to see. Are there any clients that match these email addresses? Are there any potential

1:00.7

employees that match any of these email addresses? Are there candidates that match the email

1:04.8

addresses? And so when we did that, we were lucky enough to have a hit in our applicant

1:10.1

tracking system. Now, this was not someone

1:12.5

that was making its way through the interview process with us. It was a resume that was in a bucket

1:18.2

of other resumes that was just not really being looked at yet by the recruiting team.

1:24.7

Now, when you looked at that resume, was it one that usually you would look at

1:30.7

and invite for an interview? Were there red flags in the application and the resume? Yeah, it depends

1:36.7

on what we were looking for. The person was more of a technology generalist, I would say,

1:43.1

as far as the resume was concerned.

1:45.2

There was no like standout skill set that we would have been interested in.

1:48.7

So they likely would have just been reviewed by the recruiting team, you know, put into a pile of,

1:54.6

you know, maybe someday or maybe even just sent a rejection email.

...

Please login to see the full transcript.

Disclaimer: The podcast and artwork embedded on this page are from CoinDesk, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of CoinDesk and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.

Copyright © Tapesearch 2025.