HomeVideos

Axios just got f**ked

Now Playing

Axios just got f**ked

Transcript

231 segments

0:00

Hey, how would you like to join a team's

0:02

call and then by joining the team's call

0:04

you get hacked by North Korea? Well,

0:06

that's what happened with Axios. It

0:08

would be kind of strange if you haven't

0:10

heard about the Axios hack because even

0:12

the legend himself, the modern-day poet,

0:15

the real minstrel among us all, Fireship

0:18

did release a video and I think he

0:19

summed up the Axios hack best with the

0:21

following.

0:22

>> That improved developer experience just

0:24

turned into non-consensual backdoor

0:26

penetration by a magnumsized Trojan.

0:28

That man does not mince words. Before I

0:31

tell you exactly how Axios was hacked,

0:33

let's just go over a quick couple

0:34

details for those that aren't in the

0:35

know. On March 31st, Axios was hacked.

0:39

Effectively, what happened is that Jason

0:41

ended up getting compromised. And then

0:43

by being compromised, Axios published

0:45

two new versions, 1.14.1 and 030.4,

0:50

in which involved a new library called

0:52

plain crypto.js, JS which just wraps

0:54

crypto but instead steals all the

0:56

credentials and does every you know just

0:58

completely takes advantage of your

0:59

computer. The malicious versions were

1:00

alive for about 3 hours and you should

1:02

go through and make sure you don't

1:04

actually have these just in case. If I

1:06

were you, I'd probably just roll all my

1:08

credentials everywhere, reset everything

1:10

if you happen to be hit in this. Also

1:12

kind of strange just throwing this out

1:13

there as I was reviewing the summary. Uh

1:15

right here, Victor just didn't like

1:17

Jason telling everybody about what

1:19

happened and how to fix things. Oh,

1:21

Victor, that's kind of strange, don't

1:22

you think, V? V V V V V V V V V V V V V

1:23

V V V V V V Victor, why why you dislike

1:25

him that? Well, yesterday Jason actually

1:27

gave an update on the situation and gave

1:28

us the real details of what exactly

1:31

happened to him. First, they reached out

1:33

masquerading as a founder of a company.

1:35

They had cloned the company's founders

1:37

likeness as well as the company itself.

1:39

Second, they invited me to a real Slack

1:42

workspace. This workspace was branded to

1:44

the company's CI and named in a

1:46

plausible manner. The Slack was well

1:48

thought out. They had channels where

1:50

they were sharing LinkedIn posts. Yes. I

1:53

love that. It's like, yo, how do you

1:54

know it's a real company? Oh, there's a

1:55

channel dedicated to sharing LinkedIn

1:57

posts. [laughter]

2:00

I guess honestly, I don't think I've

2:02

been a part of a real company then.

2:04

Because that sounds horrible. If I went

2:06

into somebody's Slack and they're like,

2:08

"Oh, yeah, that's where we discuss the

2:10

the the happenings of that very

2:12

well-known and very wellrespected

2:14

network, LinkedIn." I' like, "Brother, I

2:17

don't think I belong here. this this

2:18

isn't for me. Whatever's happening here.

2:20

They even had what I presumed were fake

2:22

profiles of the team of the company, but

2:25

also a number of OSS maintainers. So,

2:27

they just kind of set up this very

2:29

elaborate environment for this one

2:31

individual person to be had. They

2:33

scheduled a meeting with me to connect.

2:35

The meeting was on Microsoft Teams. That

2:38

should be a red flag. Okay. I don't know

2:39

what's going on, but but meeting on

2:41

Microsoft Teams, like I wouldn't even

2:43

write on the internet that I joined a

2:45

Microsoft Teams phone call. Okay. I

2:47

would keep that to myself. I would hide

2:49

that little piece of knowledge. The

2:51

meeting had what seemed to be a group of

2:52

people that were involved. The meeting

2:54

said something on my system was out of

2:56

date. I installed the missing item as I

2:59

presumed it was something to do with

3:00

Teams, and it was the RAT. For those

3:02

that don't know what a RAD is, a RAT

3:04

stands for remote access Trojans, or

3:06

sometimes remote administration tool. It

3:08

is a type of malicious software that

3:10

allows hackers to gain unauthorized

3:11

hidden remote control over a target

3:14

computer or device. In other words, they

3:15

can see everything you do. They have

3:17

access to every single file you create

3:19

and they're able to put anything they

3:21

want or make your computer do any

3:22

action. To be completely fair here, I,

3:25

you know, shameful enough as it sounds,

3:27

if I ended up joining a Microsoft Teams

3:29

call and then it was like, "Hey,

3:30

something's out of date. You need to

3:31

install a new driver." The chance of me

3:33

being had it could go it could go up. It

3:36

could definitely go up. The thing that

3:38

makes this so difficult is that if you

3:40

actually go and look at some of the

3:41

screenshots, it looks just like

3:43

Microsoft Teams or it looks just like

3:46

Zoom. And if you look at the web

3:48

browser, if you're not even careful

3:49

enough, that looks just like a Zoom

3:51

link. If you're not familiar with a Zoom

3:53

link, they typically look like something

3:54

like this. There's some sort of region.

3:57

Zoom US and then an ID right afterwards.

4:00

Whereas this one right here is that kind

4:02

of same region except for there's just

4:03

no dot right here. So, if you're just

4:05

not even looking at like it's a very

4:07

simple mistake to realize you're not

4:08

even on Zoom. The team one seems a

4:11

little bit more obvious though.

4:12

Microcell, like there's definitely

4:14

something going on right there that that

4:15

that that doesn't that doesn't look

4:16

real. I feel like I would not be had by

4:18

this one again. Victor, you down you

4:21

downvoted again. Hey, Victor. Hey, V.

4:23

Hey, Victor. Where were you on the

4:25

evening of the infamous Teams call? Just

4:28

a Hey, I'm just asking questions here.

4:30

Even the person that provided the

4:31

screenshots right here, Victor also

4:33

downloaded it. Strange, huh? What is

4:35

going on, Victor? All of this just goes

4:37

to show how easy it is to be had. Okay,

4:40

I assume that JSON probably knows a

4:42

thing or two about tech. Probably

4:44

doesn't get had by those simple text

4:46

messages that like, "Oh, your UPS

4:48

package is late, bro. Hey, why don't you

4:50

just click this link?" Right? It takes a

4:52

little bit more. I think I could have

4:53

been easily fooled by having something

4:55

that feels so set up, right? You go to a

4:58

Slack. There's multiple people there. It

5:00

has the company branding. It even has a

5:02

LinkedIn section, very unhinged as it

5:05

is. It has other oss maintainers. People

5:08

are yapping. Oh my gosh. Hey, we have a

5:10

meeting. Which is also strange because

5:12

one of the things apparently they do

5:13

during this meeting is that instead of

5:15

just like, hey, you should join this

5:16

meeting. Hey, you should join this

5:17

meeting. They they give you they play it

5:19

hard to get. Apparently, they'll

5:20

schedule the call for like a week out

5:22

and then they'll reschedu it for another

5:24

week being like, "Oh, hey, we can't do

5:26

it right now. Could you do it even next

5:28

week?" They really just slow roll you.

5:30

They age you like a fine bottle of wine.

5:33

It's insane because 2 to 3 weeks you

5:35

think that they would be worried about

5:37

getting caught that you would kind of

5:38

notice something's wrong with the Slack,

5:39

but no, they let it go nice and slow

5:42

because they really want to build up

5:43

that rapport that what you're about to

5:45

join is completely and absolutely above

5:48

board which apparently with other people

5:50

they actually like step through and give

5:52

them other instructions on how to

5:54

potentially fix their problem and then

5:55

at some point be like here try this

5:57

install script and then that and then

5:59

bam they get had. And this exact style

6:02

of getting hacked apparently is

6:04

identical effectively to this right

6:05

here. The UNCC 1069 targets

6:08

cryptocurrency sector with new tooling

6:09

and AI enabled social engineering. This

6:11

was just released a couple months ago by

6:13

Google. Apparently what it is is North

6:15

Korean threat actors and they're just

6:17

using more and more sophisticated

6:19

technology and the power of AI to be

6:22

able to dupe people. And they will often

6:24

use something that looks like this. Like

6:25

again this looks just like the Zoom

6:27

meeting. They just flip around the

6:29

credentials, right? So it's like us5 web

6:33

US us and then have the zoom on the

6:35

other side and just make it so

6:36

believable and then the CSS is so well

6:38

done. Hey, good job AI. That's why

6:40

that's the power of AI being able to

6:42

clone out a UI. So that's that's what

6:45

happened with Axio. So poor one out for

6:47

Jason. And also Victor Vic. Hey yo,

6:50

Victor feel like we got to know why

6:52

you're so upset at everything. Okay.

6:53

What's what's going on? What what what

6:55

are you hiding? Do you also happen to

6:57

know of a nice Microsoft Teams link that

6:59

I should join? Do you have a Slack

7:01

organization that would be something

7:03

that I could end up joining? I'm on to

7:05

you, Victor. The name is the Primagen.

7:07

Hey, do you want to learn how to code?

7:09

Do you want to become a better back-end

7:11

engineer? Well, you got to check out

7:12

boot.dev. Now, I personally have made a

7:14

couple courses from them. I have live

7:16

walkthroughs free available on YouTube

7:18

of the whole course. Everything on

7:20

boot.dev you can go through for free.

7:22

But if you want the gamified experience,

7:24

the tracking of your learning and all

7:25

that, then you got to pay up the money.

7:27

But hey, go check them out. It's

7:28

awesome. Many content creators you know

7:30

and you like make courses there.

7:33

boot.dev/prime for 25% off.

Interactive Summary

The video discusses a sophisticated hack targeting Axios, where a developer named Jason was compromised. The attackers created a fake company environment on Slack, complete with cloned company likeness, a plausible Slack workspace with a channel for LinkedIn posts, and even fake profiles of OSS maintainers. They then lured Jason into a Microsoft Teams meeting, disguised as a necessary update, which installed a Remote Access Trojan (RAT). This allowed them to gain full control of his computer. The video highlights the elaborate social engineering tactics used, including mimicking legitimate communication tools like Zoom and Microsoft Teams, and the growing sophistication of such attacks, potentially leveraging AI, as seen in the UNCC 1069 campaign targeting the cryptocurrency sector by North Korean threat actors. The speaker also humorously questions Victor's potential involvement or knowledge of similar tactics.

Suggested questions

5 ready-made prompts