Pinned Tweet
We've been on the road reporting on how small towns in America are being affected by AI.
From a town with a single Flock camera in Upstate NY... to a Mormon community of 4,000 in Utah bracing for the world's biggest data center.
Here's a preview of what's coming up from Soon.
Watching our new docs before they come out
Soon retweeted
I left NYC. For a small town. It was dope. Get out of town and meet real people
Half the breaches this month came down to API keys sitting somewhere they shouldn't.
TruffleHog is one of our favorite GitHub projects for anyone who ships code with secrets in it, which is everyone.
>it scans Git history, Slack, wikis, logs, S3 buckets, Docker images, and your filesystem for leaked credentials
>it recognizes 800+ kinds of secrets, like AWS, Stripe, Cloudflare, and Postgres passwords
>it can check whether a key it finds still works, so you can fix the live ones first
github.com/trufflesecurity/t…
If you deploy on Railway, rotate your API keys today.
Railway disclosed this morning that an unauthorized third party got into the systems where it stores customer environment variables, and was able to decrypt some of them. Those can hold API keys, database passwords, and registry credentials.
> Railway thinks it's part of a series of attacks on platform companies aimed at AI inference providers
>it has asked those providers to revoke keys proactively
>all deploys are paused while it investigates
>it's telling every user to rotate env vars and registry credentials and check their logs
An urgent notice from the Railway team
blog.railway.com/p/security-…
Why this is a big deal: Railway isn't the first company hit this month.
Zeabur, another app hosting platform, said an attacker read the environment variables in its platform database on Oct 14-15 and went looking specifically for AI service keys.
On Oct 17, OpenCode told 1.4% of its Console users that their saved OpenAI, Anthropic, and Google keys may have been exposed, and some of them say they've seen hundreds of dollars in charges they didn't make. Fireworks AI says secrets in some of its customers' accounts were captured too.
The pattern is the same every time: go after the platform where developers keep their keys, not the AI labs themselves. A stolen key works until it's revoked, so attackers can run up your bill, resell the access, or use it to pull huge numbers of model outputs to train a rival model.
Anthropic said in September that the groups doing that kind of distillation get access partly through harvested API keys.
If your keys sat in any of these platforms, revoke them with the provider itself, not just in the platform, and set spend limits.
Meta just got ordered to pay $25 billion in New Mexico over the Cambridge Analytica scandal, which happened 8 years ago.
TLDR: a Santa Fe jury decided Facebook misled people in the state about how it handles their data.
> The jury counted 43 million+ violations at up to $5,000 each, which came to $219.5B
> The judge cut it to $25B and added 15% interest a year until Meta pays
> The judge called Facebook's post-2018 investigation "willfully ineffective," citing pressure from execs to keep costs down
> This fine is 5x the FTC's record $5B fine over the same scandal, and it comes from one state
New Mexico skipped Meta's $17B settlement with the other states in August and went to trial. Now every state AG knows what a jury can do with per-violation math.
JUST IN: Meta ordered to pay $25 billion to New Mexico after jury finds company misled consumers about data privacy reut.rs/4emaeGU
"I would never use the company funds to book a private plane"
scoops! @antoniabmassa and i dug into the push and pull between polymarket investors and the prediction market's CEO, shayne coplan.
story features private jet flights, elon musk's personal lawyer, talks with goldman sachs as well as cantor fitzgerald
bloomberg.com/news/articles/…
Claude just solved a 25-year-old NSA mystery in under 30 minutes.
TLDR: The secret numbers behind some of the most widely used encryption on the internet came from a basic 1990s random number generator started from a clock reading. Anthropic discovered it has no hidden backdoor.
Some background first. In 2000, NIST adopted a set of elliptic curves for digital signatures. One of them, P-256, now sits underneath a huge share of everyday security: the HTTPS connection to your bank, many passkeys, and a lot of government systems. Each curve is built from a starting number called a seed. The NSA supplied those seeds and never said how it picked them.
That silence mattered because of what came later. In 2013, the Snowden documents suggested the NSA had pushed a backdoored random number generator called Dual_EC_DRBG into a NIST standard. After that, cryptographers had good reason to ask whether the curve seeds were hiding something too. Some projects avoided the NIST curves altogether. Bitcoin, for example, uses a different curve called secp256k1. There was even a bounty for anyone who could explain where the seeds came from.
The best lead was a story that an NSA employee had hashed a joke phrase like "Bob and Jerry rule." He died in 2023 without confirming it, and when Anthropic staff tried that lead they got nowhere.
Then someone asked an internal Claude model to work it out without giving it that hint. In under half an hour, it found that all five seeds came from the C library's lrand48 generator, started from Unix timestamps from 1997 and 1998. The P-256 seed was candidate number 1,842 from a run that began on Aug 16, 1997. Anyone can now rerun the code and get the exact same seeds.
So why should you care?
First, the encryption you use every day just got a little more trustworthy. A seed that comes from a clock and a common generator leaves very little room for the NSA to have picked a weak curve on purpose. Anthropic says nobody needs to change anything.
Second, the bigger story is how it was solved. Cryptographers chased this question for more than two decades, and an AI model cracked it over a lunch break by trying an idea the humans had ruled out. The same skill that cleared these curves could be pointed at systems that really are weak, and that's why labs are paying close attention to how good these models are getting at security work.
Read more about it here:
anthropic.com/research/ecdsa…
We got UBI before GTAVI
We’re committing a portion of Anthropic’s shares to the Anthropic Public Benefit Fund, a new wholly owned entity dedicated entirely to the public benefit.
It will start off with 5% of our shares. For every 50% increase in the company’s value over a set baseline, we can contribute up to an extra 2%, subject to our board’s discretion.
In total, this means that roughly 20% of Anthropic’s shares are committed to the public good. Our co-founders have already pledged to donate 80% of their equity, and around half our employees are donating a portion of their equity as part of a donation matching program we’ve run since our founding.
In the post below, we share more details about our new fund.
anthropic.com/news/public-be…
You can spot an AI-built website from a mile away. Purple mesh gradient, three identical feature cards, a little "01 · Capabilities" label over every section.
Taste-skill is an open-source skill that fixes that, and it's our favorite new GitHub project for anyone that actually believes that "taste is the new moat."
Before your agent writes any code, it picks an art direction and pulls real photos for inspiration. When the page is built, it opens it in a browser and checks it for the usual AI-design tells.
It works with Claude Code, Codex and Cursor. It's MIT licensed and has about 97K GitHub stars, and v2 just dropped this week. Created by @LexnLin.
github.com/Leonxlnx/taste-sk…
Watch as our very own @probablyhala rates this empty rave, alongside other events at SF tech week here : youtube.com/watch?v=KXnhuQkN…
Our own @probablyhala went around SF Tech Week events and found much pain in the world but not in this room...
Watch as she rates the most unhinged events from the week: youtube.com/watch?v=KXnhuQkN…
“AI is not going to slow down.”
@probablyhala went to the @deel padel tournament at SF Tech Week and asked attendees whether we should be slowing down AI development.
🤖 Made with AI
Watch the full video here:
youtu.be/KXnhuQkND0s
🤖 Made with AI















