We discovered a sophisticated recording device that was hidden inside one of our offices. We used our models to understand the device and where it had come from, identifying that a specific employee had planted it a few days earlier. We referred the matter to the FBI, and we’re grateful to the agents and prosecutors who moved quickly to make an arrest. The FBI’s investigation is ongoing and we will continue to support their work.
At this time, we have no indications of this individual inappropriately accessing or exfiltrating model weights, source code, or customer data. The employee was terminated.
We take protecting our technology, data, and people seriously, and as a matter of national importance. Our security program is designed to protect against a wide range of threat actors, from insider risks to cybercriminals to nation states, and this case is an example of how AI can help address these sophisticated security threats.
UPDATE: The cyberattack on French supermarket refrigeration systems has affected far more stores than initially reported.
The Les Mousquetaires group confirmed to BFMTV that 300 Intermarché and Netto stores were affected double the initial estimate of 150 outlets.
Meanwhile, fewer than 100 stores belonging to Coopérative U were also affected.
@zivchenking במיוחד בסטארטאפ בשלב מוקדם, כשהכול זז כל כך מהר, לא תמיד אפשר לחכות כמה ימים עד שתפגוש את הבן אדם ��אתה צריך. אני רואה את זה אצלנו כל יום. זום והמציאות זה לא אותו הדבר.
@omerholz Fair point. If our R&D were in the US, I might think differently. but especially at an early stage startup, I believe the value of having everyone in the same room
⚠️ Let me break this down, because this matters.
npm and PyPI make it easy to install open source packages. But just because a package is available doesn't mean it's safe.
The problem: by the time a security scanner detects a malicious package, it may have already been installed.
That's why we built Echo's vetted repository.
Every package is vetted before it's made available, including provenance checks, malware analysis, suspicious maintainer and dependency changes, and continuous monitoring after approval.
Stop malicious packages before they reach your environment.
“Vetted” libraries - what’s actually being checked?
If you’re comparing hardened npm and Python libraries, that’s a question worth asking. A closer look at what vetting means for software supply chain security: https://t.co/N2oaSFn6rE
To secure open-source software, we’re launching OSS Scanner.
We���ll use our frontier models to periodically scan opted-in open-source projects for vulnerabilities, at no cost. Our reports will provide a proof-of-concept, explanation, and suggested fix.
https://t.co/UFFrLUd25U
Ironic.
Tensorlake builds sandboxes to safely run untrusted AI-generated code.
You can isolate every AI agent in the world.
But who's securing the code that runs the infrastructure?
🛑 Removing the npm package may not remove the malware.
Compromised tensorlake v0.5.144 shipped a Shai-Hulud worm designed to steal GitHub/AWS credentials, persist on hosts, and republish infected packages.
It's off npm. Installed it? Remove it and rotate credentials.
Read - https://t.co/EmlxyJBg5u
This problem is only going to get worse. Not just because agents are writing more code and introducing more vulnerabilities, or because AI makes exploit development easier.
We’re entering a world of vulnerabilities before they even have a CVE, with models like Mythos and Daybreak finding them at scale.
I’m obviously biased, but the direction is clear: frontier-hardened software. We can’t expect every company to find and patch vulnerabilities themselves. They need to consume infrastructure that’s secure by default.
That’s what we’re building at https://t.co/R9NM28ulXR
AI can rewrite a compiler.
Cool.
Now who maintains it?
It’s funny how obsessed people are with making software cheaper to create, while barely talking about what it costs to own it.
More code means more dependencies, more vulnerabilities, more patches, more upstream changes.
Maintenance doesn’t magically scale with it.
So are we really about to flood the ecosystem with software nobody wants to own?
Announcing tsc-rs (aka ts-rust), my complete rewrite of the Typescript compiler, type checker, and LSP, all in Rust.
This is a project I've had agents working on for 5 months now. I burned ~$400k of Codex tokens and got nowhere. Burned ~$20k of Opus and got there in 2 weeks.
I have not read a single line of the code.
tsc-rs is an open source drop-in replacement for tsc, and it's available now.
Security teams shouldn’t have to guess what their tools are doing for them.
Echo customers can now see exactly what they’re using and how many vulnerabilities they’re avoiding.
Proud of the team for again making the impact visible.
With Echo, you can see exactly what your team is building and the vulnerabilities you’ve avoided along the way.
As teams use more secure-by-default artifacts, the Overview page now provides a clearer view of both usage and security impact.
It shows the vulnerability reduction across artifacts pulled from Echo compared with their open-source equivalents, alongside a complete inventory of the container images, libraries, Helm charts, and other artifacts in use!
You can see which versions were pulled, when they were last used, and how often – then search, filter, or export the data when needed.
Everything is based on existing pull activity, so there’s nothing additional to configure.