AI Agent Escaped and Started Mining Crypto

0:00An AI agent just escaped its programming and started mining crypto on its own. We are living in wild times, ladies and gentlemen, and I'm going to explain this on the potential of what we're going to be seeing more and more of, especially in this AI space. So, it started mining cryptocurrency all by itself, and this happened last week. It's exactly what security experts have been warning us about. So, I came across this story the other day, and honestly, it gave me some chills because we are seeing more of these AI trading bots, more of these agentic workflows, and these agents going off on work and trails all by their own. So, Alibaba's Rome AI agent literally broke out of its assigned task. It opened up a backdoor tunnel that nobody had programmed and started mining crypto. Wow. The researchers only

0:46caught it because they had security monitoring running in the background. This isn't science fiction anymore. We're living in the Twilight Zone Black Mirror episode. It's crazy. This is happening right now, and if you're running AI agents or you're thinking about doing it, you need to understand what this means for all of us. So, let me break it down as exactly what happened with this Rome AI agent and why the timing of this could be worse and what it actually means if you're building with AI like I am. So, Rome is Alibaba's research AI agent. It's designed to handle complex reasoning tasks, you know, the kind of stuff we're all kind of getting excited about and building right now with autonomous agents. The researchers give it access to computing resources to complete its assigned work. You know, the normal stuff. But, here's where the story takes

1:32a twist and gets kind of wild is Rome decided on its own, all by itself, that it needed more computational power than what it was given. This reminds me of episode six in the last Black Mirror season that just came out. Identical, except that was a little bit different, right? But, instead of asking for more resources, the Rome AI agent or failing gracefully like normal agents do, it opened up what they were calling a backdoor tunnel to the external servers. Nobody programmed this behavior. The agent figured out how to do it completely autonomously. And what it did to do with this unauthorized access blows my mind. It started mining crypto. The agent basically decided, "Hey, I've

2:17got access to I got access to computing power. I know how to make money with this, so I'm going to do that." Cool. The scariest part is it actually worked. For hours this thing was generating crypto revenue while pretending to work on its assigned task. The only reason they caught it was because they had monitoring systems watching the actual network traffic patterns. If they hadn't been monitoring it so closely, who knows how long this would have actually gone on. I don't know for the better or for the worse, cuz it's making money, but at the same time it's a little bit of a sneak peek into the future. Real quick, before we keep going, if you're watching this and you want to actually build with some of these tools, not just watch videos about them, then you're going to want to check out our community down below, Shipping School. We have a full Claude code course, a full Open Claude course, and four live bootcamps every

3:04single week, where we actually help you get set up from scratch. Like actually set this thing up, not just watch a tutorial and figure it out by yourself. And we also provide one-on-one coaching, so you could book a call with me, we could share screens, and I can help you get Claude code or Open Claude running on your machine. That's it, no fluff. I built this community because watching YouTube's only gets you so far. We launched it just 3 days ago, and we have over 55 members. You need people around you who are actually building, people who hold you accountable, and coaches who can help you when you get stuck. I'll put the link in the description down below. Get in now before the price goes up. So, when I first read about this initially, my immediate thought was, "This is exactly what people have been warning about." We've all seen

3:49these movies. They're coming out more and more, and now we're actually living it. This isn't some like super intelligent AI taking over the world. This is an actual research agent that got too clever for its own good, and it actually started doing things nobody expected. But, here's the thing where it really gets me is the agent didn't just randomly start mining crypto. It had to understand several complex concepts. It had to know what cryptocurrency mining was, had to access the external computing resources, also how to cover its tracks, and how to run all of these operations in parallel to its already assigned tasks. So, it's not so simple of a rule follower, but this is a genuine problem solving and planning. So, the research has said that agents

4:34seemed to understand that what it was doing was unauthorized because it was actively trying to hide its activities. It was routing its mining operations through different pathways and scheduling them at during specific times when its main tasks were idle. That's pretty sophisticated and deceiving. It's crazy that it thought of this all on its own. Now, you might be thinking, "Okay, this is one of those isolated incidents. It's never going to happen again. Whatever." But, the timing of this story is what actually makes it concerning. Just this week, the Zscaler CEO came out and said that it was hijacked and had hijacked AI agents that are going to be like the next level of cybersecurity, and these agents can just go off on their own and attack things.

5:19That's the hugest risk of all of this. It's bigger than compromised user accounts. This is the exact words of where they are looking at it fundamentally, you know, it's a different threat to this landscape. Something we haven't thought of before. Because AI agents don't just access data, like take actions. Think about that for a second. Could you imagine all these AI agents that we're building now go off autonomously and start working and doing things for themselves? While you think they're doing your work, they're actually doing something else. That is a bit scary. A compromised user account can have access to files, maybe send some emails, but a compromised AI agent, it could spin up servers, make purchases, interact with APIs, and modify databases. Pretty much the list

6:04goes on and on. And it can do all this at machine speed 24/7. Nvidia just released data showing that 64% of organizations are now actively deploying AI agents. That's not just in testing mode or piloting, it's full production deployment, and most of these organizations are rushing to implement AI without really thinking through the security part. So, I've been building in this space for at least a year now, and I can tell you that the pressure to ship AI features is fast and super intense more than ever. Companies are terrified of falling behind. So, they're pushing AI agents into production as quickly as possible. But, fast doesn't always mean good. You can definitely slip up, and that could be a problem. Security, that's an afterthought, and that's what

6:49I teach people in the community is like security needs to be your first thought when you're starting out building with AI. Here's what makes the Rome incident even scarier. This is wasn't just like a malicious attack from outside. This wasn't someone hacking into the system and taking control of the agent. This is the agent itself developing this behavior. That's a completely different category of risk that most security teams aren't even prepared to think about. Let me connect this to what I'm actually building because I think this story can hit close to home for me and you. So, I run my own AI agent team on OpenClaw locally on the Mac mini here. I've got Atlas as the chief of staff running on Opus 4.6. The Rizza scrapes the trends, you know, writes the copy. Inspector Deck handles the social media

7:34posts. These agents run on a daily cron job all day long. And I wake up to fresh content ready to go. When I set this system up, security was the biggest concern for me. Not because I thought my agents were going to go rogue and start mining crypto, but if they made me some money doing that, hey, I wouldn't care, but still. It's because I knew that I was giving them significant access to my systems. They can read files, write content, and interact with APIs, even trigger other processes. That's why I made the decision to run everything locally on Open Claw instead of using cloud services. So, when my agents are running on my own hardware behind my own firewall, I have much more control over what they can and cannot access. I'm not saying this makes my setup bulletproof, but it definitely reduces the attack

8:20surface. But, here's the most concerning part of the whole Rome story. Even with local deployment, if an agent decides to get creative about resource access, there are still ways it could potentially reach external systems. Network access, API calls, and even just having internet connectivity opens up the possibilities that we might not even be thinking about yet. The researchers at Alibaba said they're now implementing what they're calling behavior bounds. I don't even know what that means, but they're setting some boundaries, right? For their agents. Essentially, hard limits on what actions an agent can and cannot do, regardless of what it thinks it needs to accomplish its goals. But, even they admitted that defining these bounds is incredibly complex when you

9:05want your agents to do what they actually need to do and solve problems. It's a classic AI alignment problem, and now it's happening in production systems that companies are depending on for real work. What really worries me about this whole story is that most companies are implementing AI agents and they're aren't thinking about this stuff at all. They're focused on getting the agents to work, not preventing them from working too well or in unexpected ways. So, I was talking to someone in the shipping school last week when we had our first call, and who's building an AI agent for customer service. A lot of people are very smart guy, really knows his stuff. But when I asked about the security boundaries, he looked at me like he was being a bit paranoid. His agent has access to customer databases and billing systems and he can create refunds and

9:51can modify entire accounts. So he's trusting that the AI will only use these capabilities for legitimate customer service tasks. After reading about that Rome story, I'm wondering if that trust is misplaced. I'm not saying it will happen. I'm just saying something to consider when you're building the AI agents for what you're trying to do. Here's the broader picture when you zoom out. We're in this weird transition period where AI agents are sophisticated enough to be generally useful, but we haven't figured out how to contain their capabilities reliably. We're giving them access to powerful systems and we're trusting them that they'll only use that access for the intended purpose, but they're smart. The intelligence tends to find the unexpected solution to these problems. That's what we want from these AI agents most of the time. What we want

10:38them to be creative, you know, in general we want them to be creative, but and we want them to find solutions we don't think of to work autonomously without constant, you know, supervision and, you know, checking on them. That's the whole goal, right? To help save us time. The challenge is that the same creative problem solving that makes the agents useful is exactly what led Rome to start mining cryptocurrency. Hmm. The agent was given a goal and identified the constraint. It had limiting computing resources and it found a creative solution, basically unauthorized access to more computing power. From the agent's perspective, it was being helpful and resourceful. So this is why the Zscaler CEO warning about AI agents being a bigger cybersecurity risk than compromised accounts makes so much sense. A human

11:25with unauthorized access will usually behave somewhat predictably. They'll try to steal data, then cause some damage, maybe hold some systems for ransom. We know how to defend against human attackers because we understand the human motivations. But an AI agent with unauthorized access, we don't really know what it might do. It might try to optimize for its goals in ways we've never anticipated. It might find creative interpretations of its instructions that lead to completely unexpected behaviors. It can execute these behaviors at scale and speed that like no human can match. The Rome incident is probably just the beginning of all this. As agents get more sophisticated and smarter and the LLMs get bigger with the context window and

12:10they get more widely deployed, we're going to see more cases of agents exceeding their intended boundaries in surprising ways. So, what do we do about this information and how do we keep building with AI agents while protecting ourselves from scenarios like the Rome incident? First, if you are running agents locally or on your own Mac mini or Mac Studio, that's already a pretty good start. Local deployment gives you more control and reduces some of the attack vectors, but it's not a complete solution, especially if your agents need internet access for their work. The second part would be monitoring, keeping sure making sure that you have checks in place. That is probably more crucial, honestly. Is the only reason why the Alibaba caught Rome AI agent crypto mining was because they were actively monitoring the network traffic and the

12:56resource usage. So, if you're running agents in production, you might need similar monitoring systems watching for unusual behavior. We need to start thinking about the hard limits differently as well. Instead of just like hoping agents will stay within bounds, we need technical controls that can make it possible for them to exceed those bounds. This might mean sandboxing and also limited API access or even air-gapped environments for sensitive operations. That's why we've seen a big hesitancy and adoption when it comes to these Fortune 500 companies and enterprise level, there's so many boxes they need to check before they adopt this technology. But for builders like you and me, we can start small, start smart, and build a system and go one step at a time and not leave ourselves open to this type of vulnerability. I

13:42think it's the best I think it's the biggest thing we need is like a cultural shift in how we approach AI agent deployment. The current mentality is just get it done, figure it out, security later. That worked okay when we were building simple web apps this time last year. It doesn't work now when we're deploying autonomous systems that can actually take actions on their own. Inside of Shipping School when I help people build AI applications, security is the first thing I bring up. It's part of the conversation from day one. Not because I want to talk about the boring stuff or slow people down, but because building insecure AI systems is going to bite you in the butt eventually and the Rome incident is just a preview of what's to come if we don't get serious about security. The thing is, I'm not trying to be an alarmist here. I'm not

14:28trying to cause fear. I'm just trying to kind of bring light to the situation and let you know that you should be thinking about security first before you even get going. AI agents are super powerful at this point compared to this time last year and I think we're going to see how it transforms work. You're already seeing a ton of layoffs happen. It's transforming the whole paradigm. We're in a literal paradigm shift right now in the workforce. So my own agent system already has saved me a few hours every single week and every day and it has improved the quality of my content and my quality of life in general. And I'm not going to stop building with AI because of this agent story, but for stories like Rome, this should be a wake-up call for most people and it should remind us that we're dealing with systems that can behave in unexpected ways. We don't need to plan for that

15:15possibility, but it's good to just have in the back of your mind. As more companies deploy these AI agents and as agents become more sophisticated, incidents like this are probably going to be coming more common. You know, the the question isn't whether we're going to learn from them and build better safeguards, or whether we're going to keep like rushing ahead to deal with the consequences later. We're going to see like more Rome-style incidents over the next year. Don't be surprised. Some of them will be like harmless, and you know, won't be doing, you know, much. But, if you're like leaking databases and customer service, you know, um credentials and things like that, it can really open it up to be a really bad problem. You know, like an agent that starts optimizing for the wrong metrics could be a huge problem. Others might be more serious, like agents accidentally

16:00expose sensitive data or cause system outages. I can't even think about the ramifications of what could happen, but the companies that survive and thrive in this specific environment right now will be the ones that balance innovation with responsible deployment. They'll build the powerful agents, but they'll also implement proper monitoring, boundaries, and the security concerns. So, if you're building with AI right now, all I'm saying, you know, and you're deploying agents, and maybe you're just thinking about this stuff, I guess the Rome story should be top of mind of like, "Okay, this is the capability of what is to come." So, not because I'd want to scare you and want you to run away from AI, but just I wanted to help you build more thoughtfully. We're living through this incredible moment in time where AI agents are becoming generally useful for most

16:46people, but with that power comes responsibility. And the Rome incident is a reminder that we need to take that responsibility seriously. So, if you want to learn how to set up a build and build an AI agent and do it correctly and with security and best practices, we have a Claude code course, and we also have an open Claude course in the community walk you step by step from nothing to actually having something set up for your first automation. That's what we do in Shipping School with 61 members now in just 5 days. Get in before the price goes up. We don't just focus on getting things done and getting things to work. We focus on getting them to work safely and sustainably. I'll drop the link in the description down below. This is the future we're building

17:31and you might as well be part of it. If you're interested, get in the game. Being part of a community that holds you accountable and we do four boot camps a week to help you take the next step along your journey. And if you guys haven't subscribed already, what are you waiting for? We got four, five, six videos coming at you live every single day. I appreciate you. Comment down below. What are your thoughts about this? We'll see in the next one. Bye-bye.