Wow, our software security practices are really struggling.
Posts by Feross
🔥 Let's gooooo! More firepower for defending open source.
I’m speaking at AI Council 2026 in San Francisco, May 12–14.
I’ll be diving into AI security topics, including the agent attack surface and how to enable highly autonomous, trusted agents.
Hope to see you there → aicouncil.com #AICouncil
Nobody reads the code before installing it.
That’s always been the reality of open source security, but now AI is massively increasing the amount of code being written and shipped.
@feross.bsky.social breaks it down in 10 minutes on @rohdeali.bsky.social's podcast: www.youtube.com/shorts/euRDj...
🪿 There are some wild takes out there right now about open source being “dead” after recent supply chain attacks and rapid advances in AI-driven security.
Let’s talk goosenomics for a minute. → socket.dev/blog/dont-ki...
Goosonomics (noun) 🪿
A hypocritical corporate strategy of extracting immense financial value from unpaid, open-source labor, only to later declare OSS "dead" or untrustworthy to justify forking, rebuilding, and rebundling that exact same software as a premium, "safe" product.
Stay safe!
🤔
PSA: Watch out. Attackers are impersonating a Linux Foundation leader in Slack to target open source developers
Attackers are impersonating a @linuxfoundation.org leader in Slack to target #opensource developers with a multi-stage attack that ends in malware delivery. @openssf.org issued a high-severity advisory.
More details and screenshots of the lure: socket.dev/blog/attacke... #infosec
North Korea’s Contagious Interview Campaign Spreads Across 5 Ecosystems, Delivering Staged RAT Payloads
Socket
socket.dev/blog/contagi...
@socket.dev
🚀 @socket.dev's first appearance on TBPN. We talked about what's been an intense week in supply chain security and why AI is accelerating the problem.
We've been building for exactly this moment.
www.youtube.com/watch?v=EeJg...
North Korea is targeting npm maintainers.
Not for crypto. For write access to packages downloaded trillions of times a year.
Lodash. Fastify. axios. mocha. Node.js core. Even @feross.bsky.social and several @socket.dev engineers!
socket.dev/blog/attacke...
"The whole software supply chain is built on blind trust. You're downloading code from random people on the internet that you've never met, and you're like, let's just run it." - @feross.bsky.social on TBPN talking about the Axios compromise.
Full interview → socket.dev/blog/feross-...
🚀 @socket.dev's first appearance on TBPN. We talked about what's been an intense week in supply chain security and why AI is accelerating the problem.
We've been building for exactly this moment.
www.youtube.com/watch?v=EeJg...
It's absolutely unbelievable the levels of social engineering maintainers have to be alert to these days. Hopefully the general media pick up on @sarahgooding.bsky.social's story to raise awareness more widely. #npm #nodejs #security
Most critical OSS projects don’t have independent security budgets, so it's not unusual that even something as central as @nodejs.org depended on pooled funding models like the IBB. If open source consumers want these kinds of security incentives to exist, they need to step up to fund them.
this is one of my favorite parts of the @vlt.sh CLI. it uses @socket.dev security data to prevent known malware from running lifecycle scripts like postinstall!
and it’s powered by queries under the hood so you could make it as granular as you wanted (but we ship with safe defaults)
We’re seeing cases where teams can’t explain how they were compromised by the Axios incident because it doesn’t show up in their project's lockfile. The blast radius here is much larger than it looks.
Deep dive into the messy reality of modern dependency resolution → socket.dev/blog/hidden-...
⚠️ If you're running local mcp servers, you need to do the following:
1. Individually "install" packages you want to use, within a specified directory: (e.g. $HOME/mcp) creating a lockfile
2. Add: "--include-workspace-root --workspace $HOME/mcp --no --offline" to EVERY npx call
@sapcommunity.bsky.social @recap-conf.bsky.social another reason to stop using axios in SAP packages like cap or ai-sdk. Standard js APIs should suffice. Fetch is safer, lighter, and better.
Letting one get drowned in (Re)DoS vulnerabilities to the degree that one develops severe alert fatigue is dangerous. Just look at today's security incident – those things are dangerous to everyone.
New month, new GitHub bot spam notifications 🙄
We're hiring for our first VP of Engineering at Socket.
You'll work directly with @feross.bsky.social to lead and scale a high-performing, deeply technical engineering team tackling some of the hardest problems in software supply chain security.
⚡️Apply here: jobs.ashbyhq.com/socket/09d8b...
We're at RSA this week! Come by and say hi!
Supply chain attacks are accelerating, AI coding tools are creating new attack surfaces, and we've been busy building.
Find us at The Metreon (161 4th St) -- we have a private suite Mon–Thu, 8am–5pm. Book time with me here: socket.dev/book/rsa
We're at RSA this week! Come by and say hi!
Supply chain attacks are accelerating, AI coding tools are creating new attack surfaces, and we've been busy building.
Find us at The Metreon (161 4th St) -- we have a private suite Mon–Thu, 8am–5pm. Book time with me here: socket.dev/book/rsa
🚨 Breaking: Trivy Docker images are compromised.
Tags 0.69.4, 0.69.5, and 0.69.6 contain infostealer IOCs. The latest images were pushed to Docker Hub without corresponding GitHub releases. `latest` currently points to a malicious image.
Details: socket.dev/blog/trivy-d...
FYI if you're using Trivy in CI right now:
75 of 76 tags on the official GitHub Action were force-pushed to serve malware. Affects 10K+ workflows.
If you're not on v0.35.0, assume compromise.
cc: @campuscodi.risky.biz @thehackernews.bsky.social @zackwhittaker.com @bleepingcomputer.com