For most of the past decade, the conversation around regression testing tools was fairly stable. The tools got faster, the integrations got smoother, and the underlying approach stayed largely the same: write tests, run them in CI, fix failures. The fundamental model did not change much because the problem did not change much. AI-assisted development has changed the problem. When developers use AI coding assistants to generate significant portions of their codebase, the assumptions that most regression testing tools were built around start to break down in specific and consequential ways. The tools themselves have not been standing still – several have adapted meaningfully in response – but engineering leaders evaluating regression testing tools today are navigating a landscape that looks genuinely different from what it looked like three years ago. This article examines what has changed, which changes matter most for engineering teams, and how to think about selecting reg...
The threat group behind the notorious Mini Shai-Hulud worm last month put the complete source code for the malware into a GitHub repository, essentially open sourcing the threat so that other bad actors can create their own variants. GitHub reportedly took down the repository shortly after it appeared, but the damage was already done, with multiple forks created, according to Datadog security researchers. The modular framework that the threat group, TeamPCP, put into the repository included tools for credential harvesting, supply chain poisoning, and encrypted data exfiltration aimed at developer workstations and CI/CD pipelines, increasingly popular targets for attackers. The released source code also indicated evolving capabilities for persistence through the integration of AI agents and for stealing via Sigstore provenance. “The open-sourcing of a production offensive framework is not unprecedented, but it’s unusual for an active campaign,” the researchers wrote in a report...