HomeVideos

Claude Code got leaked

Now Playing

Claude Code got leaked

Transcript

332 segments

0:00

coding has largely been solved. Well, I

0:02

mean, it's been largely solved thanks to

0:04

Anthropic for releasing opensource all

0:07

of Claude code again. Yes, this is

0:10

actually the second time that Anthropic

0:12

just published all of it. Now, the last

0:15

time they did that, they went through

0:16

and DMCA all these people on GitHub. So,

0:19

just as a warning, if you happen to have

0:21

their code this time, you might find

0:22

yourself in a little bit of trouble. And

0:24

I would probably recommend not

0:25

publishing it on GitHub or downloading

0:28

it because you will be violating their

0:30

terms of service. And let's just face

0:31

it, their terms of service super

0:34

important. Oh, your little GPL license.

0:38

Yeah, that doesn't matter. They get to

0:39

use that for training, idiot. All right.

0:41

So, what actually ended up happening is

0:42

that anthropic with cloud code published

0:45

to npm all of it. All the source maps.

0:47

And if you don't know what a source map

0:49

is, it effectively allows you to have

0:50

minified JavaScript. And then if you

0:52

apply the source map, it can translate

0:54

the minified JavaScript back into the

0:56

original structure of the code. That

0:58

means 100% of the code with all of its

1:00

long names, everything that you could

1:02

possibly want is available on npm. My

1:05

assumption is it's already been taken

1:06

down at this point, but nonetheless,

1:08

Claude accidentally published it all and

1:10

people have been having a heyday. There

1:13

is some really, really, really funny

1:16

things. There's some things that are

1:18

less so funny and also it showed that

1:20

Anthropic is susceptible to the Axios

1:23

supply chain attack as well. So probably

1:25

the first thing you're thinking is how

1:27

in the world would Anthropic make this

1:29

mistake? I mean this feels kind of like

1:31

a rookie mistake, right? Well, you

1:33

remember that one time they acquired a

1:35

JavaScript runtime? You remember? You

1:37

remember that time a little bit back

1:39

ago? Well, it turns out 3 weeks ago, a

1:42

guy named Jake G, hey, pour one out for

1:44

Jake G, opens up a ticket that says,

1:46

"Buns front-end development server

1:48

source maps incorrectly served when in

1:50

production." 3 weeks ago, GitHub

1:52

actions, hey, this is probably a

1:54

duplicate issue found via cloud code. O

1:59

like, oh my gosh, you just can't make

2:01

this stuff up. 3 weeks ago, this is a

2:03

duplicate. 2 weeks ago, more Hey, by the

2:06

way, it's still running. 4 hours ago. Is

2:08

this the cause of Anthropic's

2:10

embarrassing Claude code source leak? H

2:13

I wonder why they haven't addressed the

2:14

issue. They already got paid. Oh my

2:18

gosh. Then of course from there on out

2:19

it's just been no everybody just dunking

2:21

on that. Poor Daario. Okay, can we just

2:23

pour Can we just pour one out for poor

2:24

Daario? Right now he's probably making a

2:26

very painful face and realizing that the

2:29

safety of the world might be compromised

2:31

if Claude Code's code is still available

2:34

publicly. Now, I'm not going to actually

2:35

show any of the actual code, but I will

2:38

go over some Twitter screenshots. Now,

2:40

there is a small chance I'm going to get

2:42

hit with one of them DMCA takedowns

2:44

because of this. And if they do,

2:46

brothers, we're making a video. Okay,

2:49

we're we're going to we're going to milk

2:50

that. But first, a word from our

2:52

sponsors. All right. Hey, hiring

2:54

engineers is broken right now. AI

2:56

resumes, fake profiles, and senior devs

2:58

who don't even use Vim. G2I fixes that.

3:01

Not the Vim part, the hiring part.

3:03

because they have prevetted 8,000 plus

3:05

engineers through real technical

3:07

interviews. So, you can review quality

3:10

candidates in days, not months. And I've

3:13

talked about G2I before for backend and

3:15

front-end roles. But if you're also

3:16

interested in AI roles, G2I needs to be

3:19

the first place you go and check out.

3:20

Get a 7-day trial plus $1,500 off using

3:23

my code. Visit g2i.co/prime.

3:27

But hold on, there's more. You know, I

3:29

love React Miami, right? Well, now

3:31

there's another conference called AI

3:33

Engineer that's going to take place also

3:34

in Miami, right next to React Miami. So,

3:36

if you don't want to have skill issues

3:38

like I have with AI, you need to go to

3:40

the conference. Use code Prime50 off for

3:44

50 off and I'll see you in Miami. And

3:48

let's pretend you owned say a

3:51

multi-billion potentially trillion

3:53

dollar company and which had the world's

3:54

most sophisticated AI of all time. How

3:58

would you say determine sentiment of a

4:01

prompt? Now, if you would have guessed a

4:03

hard-coded reax that determines if you

4:05

said the word dam or not, then you are

4:07

100% correct because that's what Claude

4:10

Code does. Look at this. This is on

4:12

Twitter right here. This is what they

4:13

actually do. If you if you say the word

4:15

horrible or dumbass, awful or piss,

4:17

pissed, pissing, piece of crap,

4:20

junk, what the Hell

4:22

broken, useless, terrible, awful,

4:24

horrible. you. Screw this. you. So

4:28

frustrating. This sucks. Damn it. That's

4:30

a negative pattern right there. Okay,

4:31

that means you're having some negative

4:33

patterns. There's just something so

4:34

funny about a company that just

4:36

literally has access to a model that can

4:39

determine sentiment and they're just

4:41

like, "Yeah, we can't use that. That's

4:42

like that's impossible. We're we're

4:44

going to use a 2005's white list."

4:47

Fellas, come on. Coding has largely been

4:49

solved because this style of problem

4:51

solving, it's been around for decades.

4:53

Have you ever wondered how Claude Code

4:55

does its skills? Well, it turns out

4:57

there's some very great great ones

4:59

inside the repo, including cyber risk

5:02

instructions, which is just one long

5:04

embedded string with a comment saying,

5:06

"Hey, if you're going to modify this,

5:08

you first need to go reach out to David

5:10

or Kyla. Hey, no screwing around, okay?

5:12

The safety team has hand artisally

5:15

crafted this string, and if you mess it

5:18

up, you mess it up for everybody." I

5:20

would have at least thought that these

5:21

things would have been like server side,

5:23

you know, so that way no one can mess

5:25

with this. just like no actually it's

5:27

kind of you know it's off limit so you

5:28

can't touch it blah blah blah no no it's

5:30

just it's just literally right there

5:32

also something that kind of felt really

5:34

disappointing they are actually building

5:36

a buddy like a Tomagotchi inside the

5:38

terminal apparently this is going to be

5:39

released April 1st through the 7th and

5:41

then maybe even longterm just out there

5:44

at infinitum so that way you can have

5:46

like a little terminal buddy this is

5:48

honestly like an AI lab boooo okay you

5:51

got to collect out all these buddies and

5:53

you just might if you are lucky you

5:55

could possibly get a legendary Cosmos

5:58

Hail or a Nebu Lynx. They also have a

6:02

shiny chance. So, you like this is just

6:04

full-on Pokemon cards. They're just

6:05

creating Pokemon tradable cards inside

6:07

of Claude Code. This is or really I mean

6:10

it's not even Pokemon cards. What am I

6:12

saying? This is This feels closer to

6:14

NFTTS. They're actually creating NFTTS

6:18

right now. Somebody on the marketing

6:20

team at Cloud was like, "You know what?

6:21

We need we need more Tamagotchis." Okay,

6:23

that's what I love as an elder

6:24

millennial. That that speaks to my soul

6:26

and I assume everybody using our product

6:28

is an elder millennial just like me. So,

6:30

a Tamagotchi, we're going to get some

6:32

max plans out of that. Also, they have

6:34

this weird don't blow your cover mode.

6:36

So, if you are an anthropic employee

6:38

poking around in a public repo, it has

6:41

all these rules like, hey, you're not

6:43

supposed to say that you're Claude Code

6:45

or mention that you are an AI anywhere

6:47

at any point. Don't mention anything

6:50

internally. Don't do co-authored by

6:52

lines or any other attribution. It just

6:55

seems weird, right? So any anthropic

6:58

employee is not allowed to be caught

7:00

using clawed code in public. Like what

7:03

is it? What why is that a bad thing?

7:06

Also, why are you hiding? Hiding it just

7:08

somehow makes it be like, oh yeah, yeah,

7:10

look at that. Wow, anthropic employee

7:12

using cloud code. Crazy. And instead,

7:14

it's just like anthropics trying to hide

7:16

them. Why? What are you doing? Are you

7:19

doing something naughty? It honestly

7:21

just makes you sound like a bad guy.

7:22

Again, Dario, you're being a bad guy.

7:25

You don't have to be a bad guy. Just

7:26

quit doing things that just feel slimy.

7:28

But on a more serious note, something

7:30

that I think is pretty important to kind

7:31

of talk about is that whenever these

7:33

type of things happen where a bunch of

7:35

source code gets leaked that was meant

7:37

to be hidden and there's 500,000 lines

7:40

of source code apparently spread over

7:42

1,900 files, there's just going to be

7:44

bugs and security issues that would

7:46

normally be very hard to discover. now

7:49

are just fully available. People are in

7:52

fact going to figure out how to take

7:55

like advantage of you. There's already

7:57

people kind of starting to find stuff

7:58

and luckily they're making it publicly

8:00

available, but there's a bunch of people

8:02

that are going to be holding on to

8:03

things that you won't know about. Like

8:04

this one right here, the MCP command is

8:06

wild. run claude MCP get name and it

8:09

happily spits out MCP server URLs

8:13

headers OOTH hints and for standard

8:15

input output servers the entire

8:18

environment block if your envir contain

8:20

secrets they get printed straight to

8:22

your terminal whoopsies I don't know how

8:24

this can be used but at some point this

8:27

will be used to and you will be had okay

8:30

your sweet AWS credentials for your

8:32

company yeah there's going to be a lot

8:34

of ko being ran on your behalf now

8:36

granted kro can't really actually do

8:38

anything besides for take down prod. So

8:40

probably no honestly you're safe. You

8:41

can you can leak your AWS credentials.

8:43

No one no one wants that crap. But your

8:44

Gemini credentials they're going to

8:46

want. So I just have a sneaking

8:47

suspicion that we're going to see, you

8:50

know, some issues kind of arise over the

8:52

next 6 months of uh just skills that can

8:55

take advantage of certain internal uh

8:57

setups. Because let's just face it,

8:59

Claude Code is very vibe coded. Chad GPT

9:02

called it staff level spaghetti. I

9:04

actually don't know what that means. I'm

9:06

not really sure the difference between a

9:07

junior level and a staff level

9:09

spaghetti, but nonetheless, a company

9:11

moving this fast is just going to have

9:13

so many flaws. And now it's out there

9:15

for people to be able to digest and

9:17

actually take advantage of it. This last

9:19

part is going to be I I would say just a

9:21

bigger a bigger general warning for

9:23

using Clawude just in general, which is

9:25

that they have a terms of service saying

9:28

that you cannot use Claude to build a

9:30

competing product. Now, this can get a

9:33

little bit confusing cuz what does it

9:34

mean a competing product? Well, what if

9:37

you're building an always on bot? Is

9:39

that competing with Chyros, the always

9:42

on Collad? Maybe you're building some

9:44

sort of remote planning sessions. Is

9:46

that competing against Claude? Maybe

9:48

you're coming up with some nice ways to

9:50

be able to do some kind of system

9:52

caching of memory so that users can have

9:54

more of a persistent feeling session

9:56

going on. Or maybe you're just working

9:57

on multi- aent orchestration mode. Well,

10:00

all of these Claude's also working on

10:02

and perhaps if you get just successful

10:05

enough, you might be deemed a competing

10:07

product. Don't forget there's been a

10:10

long history of companies abusing this

10:12

and I am completely convinced that

10:14

Anthropic does not like its user base.

10:16

You guys are all safety liabilities.

10:18

Okay, I'm not going to say this is going

10:20

to happen, but I also wouldn't be

10:21

surprised if it did. There's something

10:23

so hilarious about the idea that

10:26

Anthropic accidentally releases all of

10:28

its source code and then it's just like,

10:31

hey, you can't look at that. That's

10:33

actually illegal. You're not allowed to

10:34

look at that. Yeah, sure. We used all of

10:36

yours and likely used all of your, you

10:39

know, regardless of the type of license

10:41

you put on there. We definitely took all

10:43

of that, used all of it, have

10:45

approximately somewhere between 85 to

10:47

95% of it perfectly stored within our

10:50

weights and can be actively recalled

10:52

like we did with the sorcerer stone or

10:54

the philosopher stone with Harry Potter.

10:56

But hey, that hey, that doesn't count as

10:58

bad. But if you take our code, then

11:00

we're going to sue you. We're going to

11:02

come after you because we are the

11:04

correct ones. We are the holy ones. Like

11:06

I just a it's hilarious that they do it,

11:08

but b it just I just it just makes me

11:11

hate them so much more. There's

11:12

something about anthropic that just

11:16

every time I hear this guy talk, I think

11:18

he it just seems like he's becoming a

11:21

super villain over and over. It's like

11:23

he's a super villain in training. I

11:25

always thought it was going to be Sammy

11:26

Samboy Almond that was the super villain

11:28

in training. I am now convinced it's

11:30

Daario. Bro's out here villain maxing

11:33

and it just makes me feel uncomfortable.

11:35

But perhaps the best outcome of this

11:37

whole source code being leaked is the

11:39

fact that someone was able to make a PR

11:42

to Claude Code to help them open source.

11:45

And even better, the PR was generated

11:48

with Claude Code. You actually can't ask

11:51

for something funnier. All right, this

11:53

might be the longest video I've ever

11:54

recorded, so I don't know. I'm I'm I'm

11:57

sorry. Or you're welcome. A jen.

Interactive Summary

Anthropic's Claude Code had its source code accidentally released on npm, including source maps which allow for the reconstruction of the original code. This leak revealed several interesting and concerning aspects of Claude Code's development and functionality. It highlighted a surprisingly simplistic approach to sentiment analysis, using a hardcoded blacklist of negative words rather than leveraging their advanced AI capabilities. The leak also exposed internal development practices, such as a 'cyber risk' instruction string that required manual approval for modifications and a 'don't blow your cover' mode for employees. Furthermore, it revealed the development of Tamagotchi-like terminal buddies and NFT-like collectibles within Claude Code, suggesting a playful yet perhaps misguided use of resources. A significant concern raised is the potential for exploitation of security vulnerabilities and leaked credentials (like AWS and Gemini) now that the code is publicly accessible. The video also touches upon Anthropic's restrictive terms of service, which prohibit the use of Claude to build competing products, leading to questions about the definition of 'competing' and Anthropic's relationship with its user base. Ironically, a pull request to help Claude Code become more open-source was generated using Claude Code itself, adding a meta layer to the situation.

Suggested questions

5 ready-made prompts