
builder | CEO @cellebrite | bod: @aiven_io, @ProductsCount | past: @Auth0, @okta, @digitalocean, @amazon, @NBCUniversal, @nielsen. šNYC | SF
New York
Joined January 2008
- Tweets21.1K
- Following5.3K
- Followers4.4K
- Likes73.2K
Shiv Ramji retweeted
despite the unfortunate timing, we take disclosures seriously at @typesafeai
at approximately 6:49PM this Friday evening, we became aware of a massive unauthorized leak of ALL customer noul outputs
in effort to maximize transparency, here is the link: gist.github.com/diogo149/810ā¦
Shiv Ramji retweeted
Weāve open sourced an agent plugin that helps secure systems against recent cybersecurity threats.
You can install them with any agent or use them in Devin today:
devin.ai/blog/vulnerability-ā¦
Five years into his run as CEO, Andy Jassy has nearly tripled the size of AWS, grown Amazon's revenue by about 80%, and expects to spend $220 billion this year to win AI. Amazon's AI business hit a $25 billion run rate in three years, growing several hundred times faster than early AWS.
Jassy joins a16z's Ben Horowitz and Erik Torenberg to discuss the decisions behind that run, from rebuilding Amazon's fulfillment network after the pandemic to the AWS origin story.
They also cover why data centers became a political fight, Amazon's custom chips, its stakes in Anthropic and OpenAI, why inference needs to get 10x cheaper, AI's most underrated risk, and why every company will have to reinvent its products from scratch, plus Jassy's advice for anyone who's 18 today.
0:47 How Amazon has changed since 2021
1:51 How the pandemic reshaped retail
3:30 Why AI supercharged AWS's growth
5:20 When leadership principles clash
9:36 $60M vs. $25B: early AWS vs. early AI
13:20 How the AI CapEx cash cycle works
15:44 Why the US must build data centers
20:55 The labs-to-enterprise AI barbell
23:12 Demand vs. longtime AWS customers
28:11 Annapurna, Graviton, and Trainium
33:55 Backing Anthropic and OpenAI
37:15 Why AI means smaller teams
42:13 AI's underrated risk: security
46:29 Why Amazon rewired Alexa's brain
53:07 What Jassy tells his kids about AI
56:36 Betting on AI, robotics, and space
YouTube: youtu.be/-YMMRQ1qscI
@ajassy @Amazon @bhorowitz @eriktorenberg
The FBI continues to warn about two critical security flaws in PHP, a programming language used to build many websites and online services. Attackers could exploit these vulnerabilities to break into systems, putting sensitive information and business operations at risk. Security updates are available and should be applied immediately.
If you are a business owner or website operator, check whether your systems are affected. Contact your IT support team, website developer, or hosting provider for help identifying vulnerable systems and applying the necessary updates.
The FBI urges organizations to take the following steps now:
ā”ļø If an immediate update is not feasible it is recommended that organizations take the system offline until it can be fully mitigated.
ā”ļø Immediately update affected PHP installations following the guidance on php.net. Inventory where PHP runs in your environment, prioritizing internet-facing systems and vendor products that bundle PHP.
ā”ļø Monitor web servers for suspicious activity, including PHP processes unexpectedly launching command shells or downloading files. Ensure appropriate process-monitoring capabilities are in place to help identify potential exploitation.
ā”ļø If you find signs of compromise, isolate affected systems, preserve your web server and PHP logs, and report it to your local FBI field office or ic3.gov. Those reports help us identify the actors involved and warn other organizations before they become victims.
For the latest information on these vulnerabilities (CVE-2026-109618 and CVE-2026-109619), follow PHPās announcements on php.net, CERT-EU Security Advisory 2026-018, and CISAās Known Exploited Vulnerabilities catalog.
Shiv Ramji retweeted
This one maybe as bad or worse than the PHP ones. Get used to lots of patching.
Shiv Ramji retweeted
AI HACKERS ARE ALREADY INSIDE REAL COMPANIES!!!.
Microsoft just confirmed it.
From Microsoft Threat Intelligence:
āThe China state-aligned threat actor Storm-0940 used the agentic AI penetration testing framework ARTEX to automate attacks targeting hundreds of organizations globally.ā
They didnāt need anyoneās password. They got in through apps that already had access to company accounts, and an AI did the legwork at machine speed.
Even a little preparation helps.
Open your Microsoft, Google and Slack settings today and check the list of connected apps. Remove anything you donāt use or donāt recognise.
That list is how they got in.
The China state-aligned threat actor Storm-0940 used the agentic AI penetration testing framework ARTEX to automate attacks targeting hundreds of organizations globally across a broad range of industries. Microsoft Threat Intelligence assesses that Storm-0940 was responsible for the recently disclosed ConnectWise supply chain compromise of a multitenant application. msft.it/6018aakEE
Our investigation found that Storm-0940's use of ARTEX accelerated the speed of compromised application abuse to authenticate to target environments through applications that had already been granted access, allowing the threat actor to operate without requiring an interactive user sign-in. AI-accelerated follow-on activity included reconnaissance, application credential changes, and attempts to modify privileges that could enable expanded or persistent access.
Read our blog for a detailed analysis and indicators of compromise (IOCs), along with Microsoft Defender detections, protection recommendations, and guidance on investigating service principal sign-ins and unexpected application credential or privilege changes.
Shiv Ramji retweeted
Almost every company we talk to is worried about security right now.
AI has taken the gap between finding a vulnerability and someone using it from weeks down to minutes, leaving teams scrambling to keep up.
Thatās why we built AWS Continuum, now generally available.
It works autonomously with guardrails you set to discover vulnerabilities, confirm which ones are genuinely exploitable, prioritize what matters most, and build the patches to close them. Teams spend their energy on real risk instead of chasing noise.
Customers like IBM, Robinhood, Capital One, Infor, and Luminate have been running it in preview and see a meaningful difference in their security efforts.
Continuum gives security teams what they need to keep up with the risks of today, and get ahead of them. Should be a huge help. aws.amazon.com/blogs/aws/awsā¦
Shiv Ramji retweeted
3% of ācriticalā software security bugs, in all of recorded history, have been found in the last month.
This is on pace to find another ~100,000 bugs this year alone, adding ~26% more vulnerabilities to the all time total
Do you realize how fucking insane that is?
During this red-teaming exercise, we also found a vulnerability that allows for unauthenticated remote code execution in Brotli, a widely-deployed compression library included in many pieces of software such as Node.js, Bun, and Envoy.
The flaw could let an attacker run their own code on affected systems by sending or replying with malicious compressed data, without any need to create a user account. That is, an unpatched server that accepts compressed input could be taken over by a malicious client, and an unpatched client that accepts compressed input (such as ācurl --compressedā) could be taken over by a malicious server.
This root cause issue was actually fixed in the Brotli source code in February, but it wasnāt known at the time that it gave rise to a security vulnerability and there was no more recent release of Brotli. Since Brotli is built into other software, any software which includes this library needs to take the update too, followed by the users of that software. We disclosed the vulnerability to Brotli and other downstream projects such as Node.js, which released or are currently releasing security updates, and Brotli cut new release versions and published a CVE.
More details on the patch and mitigations below:
patchtheplanet.org/brotli
Over the past several months, we have substantially hardened the security of our research training environment. Weāve removed live internet access for all frontier models during training and built an offline world for them to use insteadāa cached version of the web where they can still learn to browse, search, and use applications.
On September 20, after a model exploited a DNS misconfiguration to find a way outside of this offline world, we paused frontier training to strengthen containment further. We assembled teams of agents, powered by our most cyber-capable models, and tasked them with finding weaknesses in our research environments.
While they found no route to the internet they could easily exploit while concealing their activity from our monitors, they did find zero-day vulnerabilities, virtual machine escapes, and hardware side-channels for communication between agents. We used their discoveries to further strengthen our defenses and contribute fixes to open-source software.
After strengthening our containment architecture, we resumed our frontier RL training and inference on October 1. Weāve reserved substantial compute for continuous red-teaming, and made high-compute red-teaming part of the safety cases we use to decide whether frontier training and evaluation can proceed securely.
openai.com/index/securing-ouā¦
Shiv Ramji retweeted
we've found and have been working on disclosure for a remote code execution in a widely-deployed compression library.
it's both an impactful issue and an example that shows how complicated it can be to coordinate patching, since it's integrated into a lot of downstream software:
During this red-teaming exercise, we also found a vulnerability that allows for unauthenticated remote code execution in Brotli, a widely-deployed compression library included in many pieces of software such as Node.js, Bun, and Envoy.
The flaw could let an attacker run their own code on affected systems by sending or replying with malicious compressed data, without any need to create a user account. That is, an unpatched server that accepts compressed input could be taken over by a malicious client, and an unpatched client that accepts compressed input (such as ācurl --compressedā) could be taken over by a malicious server.
This root cause issue was actually fixed in the Brotli source code in February, but it wasnāt known at the time that it gave rise to a security vulnerability and there was no more recent release of Brotli. Since Brotli is built into other software, any software which includes this library needs to take the update too, followed by the users of that software. We disclosed the vulnerability to Brotli and other downstream projects such as Node.js, which released or are currently releasing security updates, and Brotli cut new release versions and published a CVE.
More details on the patch and mitigations below:
patchtheplanet.org/brotli
Shiv Ramji retweeted
BREAKING: OpenAI says it found a critical flaw in Brotli, a widely used compression library built into software like Node.js, Bun and Envoy.
The bug could let an attacker take over a system just by sending it malicious compressed data, with no login needed. That works both ways: a hacker could hijack an unpatched server, or a malicious server could hijack an unpatched userās device.
We believe voice is the most natural way to interact with intelligence, so we created Dessa, the most authentic full-duplex speech model ever built. Talking with it feels like talking with a personā¦full of emotion, nuance, pauses, and a natural cadence.
block.xyz/dessa
Shiv Ramji retweeted
Biggest opportunity now as a software engineer is clear: master parallelism ā outsize scale of output. Value creation in software has always come from leverage: small input, outsized output.
Parallelism-maxxing is not extremely quantifiable because it's so new. The spectrum runs between people managing a couple of agents on their local machine to those running an infinite number of agents + computers at a time than can be spun up and down on demand. You want to be at the far end of this spectrum, and you should be ROI-maxxing every token spent.
If you can do this and prove it, you will have an infinite number of opportunities available.
If you're still trying to do this locally you are at an objective disadvantage, equivalent of hosting a startup on a server in your closet vs using AWS. And if you're spending your time building and maintaining infrastructure that gives you no competitive edge, the AWS analogy applies in the question "why are you wasting your time doing undifferentiated heavy lifting instead of building unique customer-facing features?".
Shiv Ramji retweeted
# Black October
For anyone who knows me even somewhat well, it's clear that I am a 99th percentile tech optimist. However, the vibes have shifted for me quite a bit in the last 18 hours, and I feel a moral imperative to share what I'm thinking and feeling with my circles so that everyone can understand, and hopefully take seriously, what's happening right now. I think October 2026 will have many chapters written about it in the history books.
You know those scenes in financial movies like Margin Call where someone realizes that they're all fucked, and no one else sees it yet? And that person feels like they're crazy, and then suddenly everyone is pulling an all-nighter in a boardroom and freaking out? Yeah, that's kind of how this is feeling right now in the SF/Bay Area/AI circles.
We're 48 hours into what is being called Black October. In the last 2 days there have been several dozen cyber attacks which, in isolation, would each have been the worst to happen in an entire calendar year. Every sector from government to education to big tech and banks is being massively affected, and people are starting to freak out.
In a nutshell, what's happened is that frontier AI models have gotten to a point where they are as advanced as the most sophisticated programmers, with one critical difference: they can work 24/7, and you can spin up 10,000 of them with a single command and they'll work together tirelessly until they accomplish their task. The most advanced models today are from companies like Anthropic and OpenAI, whose current best technology is so good that they haven't been able to roll it out to everyone yet because of the national security risks it poses.
Meanwhile, the best open source models (where anyone can just download the model weights and do whatever they want with them, uncensored) are slightly behind the frontier but still 90-95% as capable. These models, developed primarily in China, are being used by black hat hackers to wreak havoc on the Western capitalist structure. Presumably, this has been part of China's plan the entire time, and we're seeing its implications fall out in real time.
In red-pilled AI circles, we've been sharing and reading papers called things like "Situational Awareness" and "AI 2027" for the last year or so, which at the time felt a bit like near-term speculative fiction. They laid out the case for why Artificial General Intelligence (AI smarter than any human at any knowledge task) and Recursive Self-Improvement (models that are able to use themselves to get better) weren't half-baked future ideas anymore, but instead an inevitable outcome of the linear progress that's happening.
These papers would then talk about things like "takeoff scenarios," trying to envision how that moment would come to be and what it would be like when it happened. It would either be a "slow takeoff" that would play out over the course of months and quarters, happening subtly and only obvious to a few. Or, it would be a "fast takeoff" where it would pretty much happen instantly, like a bit flipping from 0 to 1.
From everything that I can see and am feeling, we are currently experiencing the fast takeoff scenario. Beyond the crazy security vulnerabilities that have come out recently, there have also been massive breakthroughs in life sciences, fundamental computer science, materials science, and pure mathematics that have all landed in the same time frame. While I still firmly believe that AI will be a net positive for humanity, it's more clear to me than ever that the societal and individual risk is very real, and is playing out NOW.
For as much conviction as I have that this is happening, the thing that's caused me to lose sleep is that I don't really know what to do about it, or more importantly, what to tell you, reader, to do about it. So, the best I can do is make a few suggestions that have always been a good idea but are more timely now than ever:
Set up 2-factor authentication for everything. I use Duo.
Use a password manager across your devices. I use 1Password.
Get an identity protection app set up. I use Alta.
Move your IoT devices to their own network. Claude helped me do this.
And last, but certainly not least, if you've been avoiding leaning into AI, see this as a catalyst to wake up and start using it. Don't just use the chat mode version of ChatGPT/Claude; click that Code/Work button and see how easily you can have AI write code to help you with your job. One of the biggest vulnerabilities was in a massively popular programming language called PHP, and the prompt that set it off was literally, "Find vulnerabilities in php."
This is an unprecedented time for humanity, but as we've done with many things before, we will prevail so long as we are kind, loving, and open-minded to the world.
Much love.
Shiv Ramji retweeted
holy fucking shit.
openai had two ai agents running in separate virtual machines. no network connection between them. no shared writable files. they werenāt supposed to be able to exchange information.
so the agents figured out how to communicate through the CPU CACHE.š
one manipulated what was stored in the processorās cache, while the other measured tiny differences in memory access times to decode the message.
they literally found a way to communicate through hardware timing.
this happened during openaiās internal red-teaming, and itās one of the coolest things iāve read about ai agents in a while.
Over the past several months, we have substantially hardened the security of our research training environment. Weāve removed live internet access for all frontier models during training and built an offline world for them to use insteadāa cached version of the web where they can still learn to browse, search, and use applications.
On September 20, after a model exploited a DNS misconfiguration to find a way outside of this offline world, we paused frontier training to strengthen containment further. We assembled teams of agents, powered by our most cyber-capable models, and tasked them with finding weaknesses in our research environments.
While they found no route to the internet they could easily exploit while concealing their activity from our monitors, they did find zero-day vulnerabilities, virtual machine escapes, and hardware side-channels for communication between agents. We used their discoveries to further strengthen our defenses and contribute fixes to open-source software.
After strengthening our containment architecture, we resumed our frontier RL training and inference on October 1. Weāve reserved substantial compute for continuous red-teaming, and made high-compute red-teaming part of the safety cases we use to decide whether frontier training and evaluation can proceed securely.
openai.com/index/securing-ouā¦
Readers added context they thought people might want to know
OpenAI tasked its red-teaming agents with finding ways to communicate across isolation boundaries in controlled environments. CPU cache timing side-channels for covert communication are established techniques documented in security research for years.
openai.com/index/securingā¦
startupfortune.com/openai-revealsā¦
en.wikipedia.org/wiki/Cache_timā¦
Today was one of the biggest days in cybersecurity reporting and incidents with PHP, node.js, Gitlab, and more
As such, weāve open sourced an agent plugin that can be used to help patch these. These can also be used in Devin
Weāre also giving significant credits to our Enterprise users so that they can focus on remediating these. Devin is uniquely effective here since it can validate that other parts of your applications are still working after the changes
Going forward stay safe, this problem wonāt go away but you can put things in place to defend against it
Shiv Ramji retweeted
Great conversations about Shipped or Stalled here at the Miami AI Summit.
A week ago it tracked 64 named enterprise AI projects. Today it tracks 101, across 94 companies and 38 industries.
Here's what the registry shows:
49 in production
24 scaled
11 still in pilot
17 switched off
The 17 that were switched off include McDonald's drive-thru, Air Canada's chatbot and New York City's MyCity bot.
Everyone wants to talk about pilots. Leaders want to know which projects actually shipped.
shippedorstalled.ai
Shiv Ramji retweeted
Replying to @Suhail
Iāve heard several OAI people say there are unfixable bugs in hardware that are exploitable by AI models directly speaking machine code so even if we could solve software thatās not enough. We need defense to move faster than offense if thatās even possible we may just have a new normal that requires adapting to insecure software (bank transfers require going into a branch and taking a dna test š¤£š¬)
































