Security
A trojanised editor extension yielded access to 3,800 internal repositories
The attack harvested cloud credentials, package registry keys and AI tooling configuration files.
An editor extension yielded access to 3,800 internal repositories
The attack harvested cloud keys, package credentials and the file that says what the AI assistant can reach. The same month, sector figures showed spending above revenue.
Business
A company loses $1.22 for every dollar of revenue
Quarterly figures show about $25 billion in annualised revenue against $30 billion in spending.
From the studio
The developer's computer became the company's most concentrated asset
A criminal group compromised roughly 3,800 internal repositories through a trojanised code editor extension. What it took describes the problem well: cloud keys, package publishing credentials and configuration files from assisted coding tools.
That last item is the new one. An assistant's configuration file holds interface keys and the list of systems the assistant may reach, functioning as an access map already tested and working.
The attack's reach didn't come from the technique, it came from habit. Extensions install by individual decision, without review, and run with the developer's access, which usually includes credentials for several projects, with no short expiry.
The fix is familiar, cheap and unpopular because it annoys slightly every day: credentials that expire in hours, scope per project rather than per person, keys outside the repository, and review of what each installed tool can reach. None of that would have stopped the extension entering, and all of it would have reduced what it took.
In this issue
Business
Two frontier companies announce enterprise service ventures hours apart
The arrangements aim to create a new channel for selling AI inside large companies.
AI
A coding model rises to 69.2% on a real-task benchmark
The number comes from a test using actual repository problems rather than synthetic exercises.
Business
A funding round closes at a $965 billion valuation with a confidential IPO filing
The figure surpasses its competitor and arrives alongside a move toward listing.
Regulation
A jury decides in under two hours that a suit against an AI company is time-barred
The decision removes a legal obstacle from the path to a public offering.
Tools
Large platforms prepare their answer in coding tools
Two cloud companies target the category the model makers got to first.
Security
AI tooling configuration becomes a valuable target for attackers
The file holds interface keys and the list of what the assistant can reach.
Business
Separate credits for agent builders acknowledge different consumption
Agent use spends differently from conversation, and one bucket penalised the advanced case.
Work
An editor extension arrives without review and leaves with production credentials
The entry point of the attack is the same thing that makes development environments productive.
Business
The cost of serving the product is what separates this race from earlier ones
Growing users increases losses while unit cost depends on power and memory.
AI
Benchmarks with real repository problems become the category's yardstick
Testing on an existing codebase measures something different from solving isolated exercises.
Work
A separate deployment venture admits the product alone isn't enough
Selling access reaches those who already know how to build; large companies need someone to make it work.
Security
A credential harvested from one machine works across many projects
The number of repositories reached comes from missing expiry and missing scope.
Business
The sector's two largest head toward listing almost together
One filed confidentially; the other had a legal obstacle removed the same month.
Work
What the month teaches about the developer's machine
Self-installed extensions, credentials without expiry and assistant configuration form one problem.
Sections