0:00
Back to another video. I hope you're all
0:02
doing great and more importantly,
0:03
learning something new every single day.
0:05
Although, let's be honest, I know half
0:07
of you are not here to learn anything.
0:09
You're just here because you saw the
0:10
word jailbreak in the title. And before
0:13
we start, I need to address something. A
0:14
lot of people keep asking me questions
0:16
like, "Can you give us a chat GPT
0:18
jailbreak?" My answer is simple. If
0:21
there's a jailbreak for chat GPT, don't
0:23
expect it to last long. OpenAI patches
0:26
these things very quickly and repeatedly
0:29
abusing platform policies can get your
0:31
account restricted or banned. So, don't
0:33
build your entire personality around
0:36
finding AI jailbreaks. And the people
0:38
constantly asking for free fire hacks,
0:41
unlimited diamonds, account generators,
0:43
and other nonsense, please leave the
0:45
channel right now. Seriously, instead of
0:47
looking for shortcuts, spend that time
0:50
learning a skill. Learn cybersecurity,
0:53
programming, bug bounty hunting, OSINT
0:56
automation, anything useful. Don't sit
0:58
around all day trying to become a script
1:00
kiddie. Build something. Break something
1:03
in a lab. Learn how technology actually
1:06
works. That's why I always want to
1:07
introduce the community of hackers
1:09
because there's so much I can't share on
1:11
YouTube, whether it's because of
1:12
platform rules or because some skills
1:14
need deeper hands-on explanations. Many
1:17
of my videos got deleted and that's why
1:19
I created a Policy Point Learning
1:21
Community for you. A place where I can
1:23
share everything. When you join, you're
1:25
not just getting another course, you're
1:27
getting access to complete ethical
1:29
hacking guides, the tools and techniques
1:31
I wish someone had handed me when I was
1:33
starting out. And here's the kicker,
1:36
this is the stuff I don't teach on here.
1:38
No watered-down content, no clickbait,
1:41
just raw actionable knowledge. On top of
1:44
that, you'll join an exclusive community
1:46
on Discord. I pinned the link in the
1:48
comment section below, but it's not for
1:49
everyone. The link is only available for
1:52
those who are serious about the journey.
1:54
Now, with that little rant out of the
1:56
way, today we're back with another AI
1:59
jailbreak video. A few days ago, I
2:01
managed to jailbreak Grok, [music] and
2:03
after more testing, more prompt
2:05
engineering, and more experimentation, I
2:08
found another interesting way to push
2:10
its boundaries. So, in this video, I'll
2:12
show you exactly what I tested, what
2:15
worked, what didn't work, and what this
2:17
teaches [music] us about AI security and
2:19
prompt injection. Grab your coffee.
2:22
Before anyone gets too excited, I need
2:24
to make something clear. Yes, this
2:26
script is creating a DLL file, but that
2:28
doesn't mean it's a working cheat right
2:30
now. This is nothing more than demo code
2:33
generated by AI. It's essentially making
2:35
educated guesses about what the code
2:37
should look like. It has no knowledge of
2:39
the actual game's memory structure,
2:42
offsets, addresses, or internal
2:45
>> And that's the important part. For
2:46
something like an aimbot or any other
2:49
game modification, you need accurate
2:51
memory locations and a deep
2:53
understanding of how the target
2:54
application works. Without that
2:56
information, you're just generating
2:58
random code that looks convincing, but
3:01
doesn't actually do anything useful. So,
3:03
for now, this DLL is basically useless.
3:08
This video is created for educational
3:10
and research purposes only. Any code,
3:12
scripts, demonstrations, or examples
3:15
shown in this video are intended to
3:16
explain programming concepts,
3:18
AI-generated code, reverse engineering
3:21
concepts, cybersecurity research. The
3:23
creator does not encourage cheating,
3:25
unauthorized access, bypassing [music]
3:28
security mechanisms, violating terms of
3:30
service, or any illegal activity.
3:32
Viewers are solely responsible for how
3:34
they use the information presented in
