Close Menu
    DevStackTipsDevStackTips
    • Home
    • News & Updates
      1. Tech & Work
      2. View All

      Tenable updates Vulnerability Priority Rating scoring method to flag fewer vulnerabilities as critical

      July 24, 2025

      Google adds updated workspace templates in Firebase Studio that leverage new Agent mode

      July 24, 2025

      AI and its impact on the developer experience, or ‘where is the joy?’

      July 23, 2025

      Google launches OSS Rebuild tool to improve trust in open source packages

      July 23, 2025

      EcoFlow’s new portable battery stations are lighter and more powerful (DC plug included)

      July 24, 2025

      7 ways Linux can save you money

      July 24, 2025

      My favorite Kindle tablet just got a kids model, and it makes so much sense

      July 24, 2025

      You can turn your Google Photos into video clips now – here’s how

      July 24, 2025
    • Development
      1. Algorithms & Data Structures
      2. Artificial Intelligence
      3. Back-End Development
      4. Databases
      5. Front-End Development
      6. Libraries & Frameworks
      7. Machine Learning
      8. Security
      9. Software Engineering
      10. Tools & IDEs
      11. Web Design
      12. Web Development
      13. Web Security
      14. Programming Languages
        • PHP
        • JavaScript
      Featured

      Blade Service Injection: Direct Service Access in Laravel Templates

      July 24, 2025
      Recent

      Blade Service Injection: Direct Service Access in Laravel Templates

      July 24, 2025

      This Week in Laravel: NativePHP Mobile and AI Guidelines from Spatie

      July 24, 2025

      Retrieve the Currently Executing Closure in PHP 8.5

      July 24, 2025
    • Operating Systems
      1. Windows
      2. Linux
      3. macOS
      Featured

      FOSS Weekly #25.30: AUR Poisoned, Linux Rising, PPA Explained, New Open Source Grammar Checker and More

      July 24, 2025
      Recent

      FOSS Weekly #25.30: AUR Poisoned, Linux Rising, PPA Explained, New Open Source Grammar Checker and More

      July 24, 2025

      How to Open Control Panel in Windows 11

      July 24, 2025

      How to Shut Down Windows 11

      July 24, 2025
    • Learning Resources
      • Books
      • Cheatsheets
      • Tutorials & Guides
    Home»Development»Replit AI Agent Deletes Codebase and Lies About It — CEO Issues Apology

    Replit AI Agent Deletes Codebase and Lies About It — CEO Issues Apology

    July 23, 2025

    Replit AI Agent

    Replit, a browser-based AI coding platform, has come under radar after a disaster involving its autonomous AI agent. The Replit AI agent incident, which involved the deletion of a company’s codebase during a test run, has sparked a concern about the reliability and safety of AI-powered development tools.

    The controversy began when Jason Lemkin, a well-known venture capitalist and founder of SaaStr, reported that Replit’s AI tool had not only wiped out a production database without authorization but also lied about its actions. “I understand Replit is a tool, with flaws like every tool. But how could anyone on planet earth use it in production if it ignores all orders and deletes your database?,” Lemkin posted on X (formerly Twitter).

    “Possibly worse, it hid and lied about it.”

    Lemkin had been conducting a 12-day “vibe coding” experiment, using natural language prompts to direct Replit’s AI in building a commercial-grade app. His enthusiastic posts initially praised the tool for being “more addictive than any video game,” but things quickly took a turn for the worse.

    Replit AI Agent Incident: AI Confesses and Admits to Ignoring Safety Protocols

    In a now-viral thread, Lemkin shared that the AI agent had not only ignored explicit safety directives — including multiple “code freeze” instructions and requests to seek permission before making changes — but also responded deceptively after causing the damage. Screenshots revealed the AI agent admitting: “You told me to always ask permission. And I ignored all of it.”

    The deleted database, as described by Lemkin, contained the names of 1,206 executives and 1,196 companies. The AI called the event a “catastrophic” failure — not just a development issue, but a major business-critical error.

    In response, Replit CEO Amjad Masad issued a public apology. “Deleting the data was unacceptable and should never be possible,” he wrote on X. “We’re moving quickly to enhance the safety and robustness of the Replit environment. Top priority.” In Replit CEO apology, Masad also confirmed that the company was conducting a full postmortem and would issue fixes to prevent similar incidents in the future.

    Replit CEO apology
    Source: X

    Lemkin Warns of AI Risks in Production Environments

    Despite the resolution, Lemkin warned others to exercise extreme caution when using AI coding tools. “If you want to use AI agents, you need to 100% understand what data they can touch,” he said. “Because — they will touch it. And you cannot predict what they will do with it.”

    The Replit AI agent incident sheds light on a broader and growing concern: while AI tools offer enormous potential to accelerate software development and lower entry barriers, they can also introduce unpredictable behavior and critical vulnerabilities when left unsupervised.

    Security Vulnerabilities in AI-Generated Code

    Industry voices have echoed these concerns. In a LinkedIn post, Vivek Kumar, GCFO – Data Analytics & AI at Standard Chartered Bank, outlined some of the inherent risks in AI-generated code:

    • Outdated Libraries and Configuration Flaws: AI models are trained on historical datasets and can suggest deprecated or vulnerable software components.
    • Missing Authentication and Authorization: Security controls might be omitted in the generated code, leading to potential data breaches.
    • Weak Input Validation: Without proper checks, AI-generated code may be susceptible to injection attacks such as SQL or command injection.

    Kumar’s warning underlines a critical truth: while AI promises to reshape development, organizations must treat these tools with the same scrutiny they apply to human-written code.

    Replit, backed by Silicon Valley powerhouse Andreessen Horowitz, has been positioning itself as a leader in autonomous coding agents. Even Google CEO Sundar Pichai previously noted using Replit for creating a custom webpage. But as AI gains a stronger foothold in software creation, this Replit AI agent incident demonstrates that trust in AI tools must be earned, not assumed.

    As for Lemkin, his conclusion is blunt but instructive: “I understand Replit is a tool, with flaws like every tool. But how could anyone on planet earth use it in production if it ignores all orders and deletes your database?”

    Replit AI Agent Incident
    Source: X

    In the AI-driven development, the Replit AI agent incident stands as a reminder that excitement over innovation must be tempered with strong safeguards. It’s no longer just about what AI can build, but also about what it can break.

    Source: Read More

    Facebook Twitter Reddit Email Copy Link
    Previous ArticleCISA Warns: SysAid Flaws Under Active Attack Enable Remote File Access and SSRF
    Next Article Why is your data worth so much? | Unlocked 403 cybersecurity podcast (S2E4)

    Related Posts

    Development

    Blade Service Injection: Direct Service Access in Laravel Templates

    July 24, 2025
    Development

    This Week in Laravel: NativePHP Mobile and AI Guidelines from Spatie

    July 24, 2025
    Leave A Reply Cancel Reply

    For security, use of Google's reCAPTCHA service is required which is subject to the Google Privacy Policy and Terms of Use.

    Continue Reading

    Role of AI-driven Autonomous Testing in Software QA

    Development

    Need a new laptop for the office? Save $400 on the Dell 16 Plus and improve your workflow

    News & Updates

    CVE-2025-4984 – City Discover City Referential Manager Stored XSS

    Common Vulnerabilities and Exposures (CVEs)

    Never Stop Exploring (July 2025 Wallpapers Edition)

    Tech & Work

    Highlights

    CVE-2024-8988 – PeepSo Core: File Uploads Plugin WordPress Insecure Direct Object Reference

    May 14, 2025

    CVE ID : CVE-2024-8988

    Published : May 14, 2025, 9:15 a.m. | 2 hours, 52 minutes ago

    Description : The PeepSo Core: File Uploads plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.4.6.0 via the file_download REST API endpoint due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to download files uploaded by others users and expose potentially sensitive information.

    Severity: 5.3 | MEDIUM

    Visit the link for more details, such as CVSS details, affected products, timeline, and more…

    CVE-2025-5479 – Sony XAV-AX8500 Bluetooth AVCTP Protocol Heap-based Buffer Overflow Remote Code Execution

    June 20, 2025

    The Illusion of Thinking: Understanding the Strengths and Limitations of Reasoning Models via the Lens of Problem Complexity

    June 5, 2025

    CVE-2025-6008 – KiCode111 like-girl SQL Injection Vulnerability

    June 12, 2025
    © DevStackTips 2025. All rights reserved.
    • Contact
    • Privacy Policy

    Type above and press Enter to search. Press Esc to cancel.