Socket

Socket is the #1 software supply chain security platform. Next-gen SCA + SBOM + 0-day prevention. LOVED BY DEVELOPERS. 👀 @npm_malware

[Socket @SocketSecurity]

Today is a big day for Socket.

https://t.co/ap7eFSvIHF

[Feross @feross]

Today is a big day for @SocketSecurity. We just raised a $60M Series C at a $1B valuation, led by @ThriveCapital with participation from @a16z, @AbstractVC, and @CapitalOne Ventures. Total funding is now $125M.

Four years ago, we started Socket because open source dependencies were flowing into production faster than anyone could vet them. AI has massively accelerated that. Code is being written, shipped, and deployed before any human reads it. Security has to operate at that same speed.

One data point from Thrive's diligence that I keep coming back to: they first discovered Socket because @cursor_ai, @OpenAI, and @AnthropicAI all independently told them it was the most important security tool they'd adopted for AI-driven development. Three of the most sophisticated AI companies converging on the same vendor unprompted.

Since our Series B, Socket has grown to more than 20,000 organizations, protecting over 1.5 million repositories and blocking more than 1,000 supply chain attacks every week. The team is now over 100 people.

Three out of five FAANG companies are Socket customers. So are the companies building the most ambitious AI products: @AnthropicAI, @cursor_ai, @xai, @figma, @vercel, @Replit, @scale_AI, @GustoHQ, @Mercadolibre, and @cribl_io, alongside Fortune 100s in financial services and global media.

What we've shipped since the last round:

• Socket Firewall blocks malicious packages at install time, before they reach a developer's laptop or CI pipeline. Free for everyone.

• Reachability analysis via our acquisition of Coana, eliminating 50-80% of irrelevant vulnerability alerts by focusing only on CVEs that are actually exploitable.

• Socket Certified Patches for remediating exploitable CVEs in seconds without waiting on upstream maintainers.

• Coverage extending to browser extensions, editor extensions, MCP servers, and AI tools via our acquisition of @secureannex.

When the Axios compromise hit, our detection systems flagged the malicious dependency within six minutes. Within 24 hours, more than 2,000 organizations onboarded to Socket to block it.

Where the funding goes: deeper investment in Firewall, massively expanding Certified Patches, moving protection closer to every point of install across the developer toolchain, and new product launches pushing Socket into a category we haven't entered before.

We're hiring across engineering, sales, customer success, and threat intel.

❤️ Thank you to our customers, investors, and the open-source community for your support. Together, we’re making software safer for everyone.

[Feross @feross]

Chainguard received PHP’s fix for two critical RCEs under embargo, like every other distributor. On October 21 at 07:41 UTC, more than six hours before the coordinated release, it published built images containing that fix.

The PHP Foundation’s postmortem says Chainguard unilaterally broke the embargo. From that point, any attacker could study the fix in binary form while every other PHP user was still waiting.

CVE-2026-109618 and CVE-2026-109619 let attackers run code on web servers without logging in. PHP runs 69% of websites whose server-side language is known.

The embargo was already under strain. The CVE IDs leaked the day before, and Calif accidentally posted an exploit video that evening. PHP pulled the release forward a day but held it until 14:00 UTC, because distributors were still packaging and an immediate release would have left many users without a clean way to update. Chainguard went first anyway.

Chainguard CEO Dan Lorenc says several vendors in the disclosure had reported exploits in the wild, and that he notified the group right after making the call. He did not name the vendors or publish evidence. PHP’s security team found no working public exploit by release time. Lorenc has since apologized for the added stress on PHP’s maintainers.

Chainguard’s disclosure policy allows it to shorten timelines when exploitation is active. The patch it shipped was PHP’s, shared under PHP’s embargo.

In July, Lorenc wrote: “Pre-disclosure protection extends exactly as far as the people you can vet and hold to an embargo.”

Coordinated disclosure only works if everyone holding the fix ships at the same moment. When one party goes early, the fix becomes a map for attackers, and the users still waiting carry the risk.

PHP owned its part. Its postmortem calls the long delay in fixing the underlying bug, first spotted in a 2024 audit, “a structural failure.” It is asking the companies that run on PHP to fund more engine engineers.

If you haven’t patched: update the PHP runtime itself, not just WordPress or your framework, to 8.5.12, 8.4.27, 8.3.36, or 8.2.35. Then restart your workers.

[Rhys @RhysSullivan]

Thankfully I think that’s about it for the security vulnerabilities and we probably won’t find any more

[Andrew Becherer @andrewbecherer]

When agents become the interface, what replaces the security controls the UI provided?

Tomorrow at AGNTCon + MCPCon, I’ll debate that with Dexter Horthy, Ian Livingstone and Scott Sanders. Allie Howe moderates.

Oct. 22, 2:55 p.m. PT. Come join us.

[Socket @SocketSecurity]

The PHP Foundation says Chainguard unilaterally broke the embargo and published built images containing the critical RCE fixes more than six hours early:

“This disregarded weeks of work by many parties toward a coordinated disclosure.”

https://t.co/30TTrAH6K7

[tuckner @tuckner]

Just used LiteLLM to create my first PHP website. The AI even suggested getting a certificate from eMudhra for HTTPS to protect my login page. The future looks really bright 🥳

[Justin Elze @HackingLZ]

again? https://t.co/wl9BfTuqis

[Socket @SocketSecurity]

The vulnerabilities let attackers execute code on web servers without logging in. Cloudflare is already seeing exploits in the wild.

Changing php.ini settings won't fully protect you. WAF rules are a stopgap. Patch the PHP runtime now.

https://t.co/Je6dVobtCX

[Socket @SocketSecurity]

🚨 PHP has released emergency patches for two critical RCE vulnerabilities. Organizations unable to patch are advised to take affected systems offline.

Believe it or not, PHP still runs an enormous amount of the web. And nearly half of #PHP sites run EOL versions.

[Socket @SocketSecurity]

Socket flagged all seven malicious wheels within seven minutes of publication.

The malware runs at Python startup, even without importing LiteLLM. The release workflow built container images from a lookalike repository.

Full analysis: https://t.co/D1zoC7fx5H

[Rafał Łoś 🇵🇱 @Wh1t3Rabbit]

Don't look now, but this is problematic.
credential-stealers suck.

[Socket @SocketSecurity]

Socket flagged all seven malicious wheels within seven minutes of publication.

The malware runs at Python startup, even without importing LiteLLM. The release workflow built container images from a lookalike repository.

Full analysis: https://t.co/D1zoC7fx5H

[Socket @SocketSecurity]

🚨 LiteLLM, a Python package for connecting to AI model providers with 92M+ monthly downloads, has been compromised.

Version 1.107.0 ships credential-stealing malware through PyPI wheels and Docker images, targeting cloud credentials, developer secrets, and AI tools.

[Socket @SocketSecurity]

.@vltpkg 1.5.0 links agent skills from your dependencies to coding agents, with versions pinned by your lockfile.

The default skills filter uses Socket data to exclude packages flagged as malware before their instructions reach your agents.

https://t.co/bNunYgaJwn

[🦋 @ruyadorno.com @ruyadorno]

Given that the vlt CLI is a proper package manager, you get all the benefits like a lockfile and automatic filter of undesirable packages using data from our partner @SocketSecurity

Read more about this release in our blog post:
https://t.co/g7Rn5ba4eF

[Socket @SocketSecurity]

🧊 Rust 1.100 will let developers put fresh dependency releases on ice.

Cargo’s opt-in cooldowns give researchers and maintainers time to catch malicious crates before more projects pull them in.

https://t.co/ekfAV9Hvn2

[Socket @SocketSecurity]

Don't tell Michael Scott the bankruptcy system is down

[Socket @SocketSecurity]

Deno spent years persuading developers to bet on a better runtime. Now its creator sees “marginal” gains in a project “sucked into the gravity well of node compatibility.”

The backlash, the forks, and how AI is changing the future of JavaScript runtimes.

https://t.co/dmE6VTgKuT

[Socket @SocketSecurity]

Deno spent years persuading developers to bet on a better runtime. Now its creator sees “marginal” gains in a project “sucked into the gravity well of node compatibility.”

The backlash, the forks, and how AI is changing the future of JavaScript runtimes.

https://t.co/dmE6VTgKuT

[Sarah Gooding @sarahgooding]

The stuff of nightmares. 😵