I joined @infisical 3 years ago as the second hire, back when we worked out of a coworking space. Today we announced our $40M Series B led by Elad Gil, and we’re securing 10B+ secrets a day. So proud of this team. We're still just getting started!
We’re hiring for almost every role right now. If you want to work on real problems with the brightest minds in the field, come join us. infisical.com/careers
Given the hellscape that cybersecurity is in today (largely due to front-tier AI models), security companies like Infisical have no choice but to always stay ahead of the curve.
Today, we are announcing our 40M$ Series B at a 600M$ evaluation!
Today, we’re announcing Infisical’s $40M Series B at a $600M valuation, led by @eladgil.
AI has made it 10x easier to write code, 10x easier to find vulnerabilities, and given autonomous agents access to some very sensitive systems.
The problem is that much of today’s security infrastructure wasn’t built for any of this.
We’re changing this with @infisical. Today, over 1,300 organizations trust us to secure their infrastructure, including Airbus, First American Financial, Hugging Face, OpenRouter, and Wise.
Proud of what our team has built so far. Even more excited about what we have ahead of us.
Back to work.
The level of incompetence and negligence uncovered by the whole eMudhra incident is beyond me, this is probably on par with the Heartbleed incident from 2014, which took years to fully fix.
It really fires me up how something this stupid is allowed to happen in 2026…
The eMudhra compromise is an absolute joke. This isn't a standard data leak it's pure, unadulterated structural incompetence.
8 globally trusted intermediate CA keys were generated with basically zero cryptographic entropy. 😠 A standard NIST P-384 private key needs 384 bits of entropy so it's mathematically impossible to crack.
Yet, the blokes at @eMudhra generated production keys with 3 to 8 bits. The actual private key values were literal single digits like 4, 56, and 115. This is playground-level stuff. Infuriatingly amateur.
How does a private company with zero fundamental grasp of public key infrastructure even get global root trust? Indian regulatory and auditing bodies make us look like complete idiots. They treat cybersecurity like a casual compliance checkbox instead of critical national infrastructure.
This failure leaves the entire internet with a massive cleanup job. Browsers blocked these keys fast, but millions of unmaintained Linux distros, embedded IoT tech, Docker containers, and backend apps are completely exposed out there.
If you're an everyday user (not a developer), you still need to fix this on your personal devices right now:
Update everything: Force-update your web browsers (Chrome, Edge, Firefox, Safari) and your operating systems across your laptop, Mac, and mobile phone. Don't wait for auto-updates manually trigger them in your settings.
Test your device: Go to emudhra.we-have-a-problem.co…
Verify the result: If your browser blocks the site and says "Did not connect" (or throws a certificate error), you are safe. If the website opens normally, you are still vulnerable.
If you're running Linux, Python, Go, or Node infrastructure:
Stop what you're doing. Manually update your ca-certificates bundles, pins, or drop a system-level blocklist immediately to prevent traffic interception.
The casual negligence of these agencies shouldn't be your vulnerability.
can we as engineers please come together as a collective and all agree that just because something >>can<< run in kubernetes, doesn't mean it should
Daniel retweeted
A credential an AI agent can read, is a credential it can leak.
Introducing Agent Vault: a new Infisical product that lets Claude Code, Codex, and other agents call the APIs and services they need, without holding real credentials.
With Agent Vault:
> Your agents work as they normally do, with no code changes
> A prompt-injected agent can only reach preapproved HTTP services, down to exact methods and paths
> Agent sessions expire on a schedule you set, and every request is logged
using github is a liability these days
We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we le... githubstatus.com/incidents/3…
Daniel retweeted
If your agents run in @daytonaio sandboxes, you can now manage their keys in Infisical alongside every other secret your team uses!
Infisical now syncs copies of secrets straight into Daytona's secret store. Daytona keeps the real values out of the sandbox, and Infisical keeps the secret values current. Rotate a key in Infisical and every sandbox that references it gets the new value on the next sync, with no changes to your create calls.
Available on all plans, including free!
Daniel retweeted
You can now give someone access to production Redis without giving them the password!
You put the password into Infisical once. After that, you decide who has access. Anyone with permission can open Redis from their browser or terminal without ever seeing the password. Infisical keeps logs for every command.
Live in Infisical PAM today! If you haven't looked at Infisical for privileged access management yet, the list of supported account types is growing every week. Docs below 👇
Daniel retweeted
introducing Access Controls v2 in Infisical!
you can now grant one-off access to a single folder or environment in just a few clicks without needing to create custom roles
Daniel retweeted
New in Infisical: Postgres account discovery!
Infisical PAM can now scan your Postgres instances and surface every account that can log in, including the ones no-one is tracking. Pick the accounts you want to bring under management, and rescan on a schedule to catch what changes.
No network exposure: the scan runs through your Infisical Gateway.
Live today on Enterprise. See it in action 👇
Daniel retweeted
You asked. We built it.
The Infisical Community is live.
Your place for Infisical discussions, feature requests, roadmap updates, announcements, and feedback.
Come hang out → community.infisical.com/
Daniel retweeted
Infisical now writes your secrets into your Spacelift contexts!
You choose an Infisical folder and the @spaceliftio context to write to. When a value changes in Infisical, Infisical updates the context, and every stack attached to it gets the new value on its next run, with support for environment variables or mounted files.
Available on all plans.
Daniel retweeted
Rotating @Cloudflare API tokens shouldn’t break prod!
Infisical now rotates Cloudflare API tokens and R2 access keys for you. The new credential gets issued alongside the old one, and both are live until the next rotation. Set the interval, walk away, and leave manual secret rotations in the past.
Live now on Infisical Enterprise 👇
Daniel retweeted
New in Infisical: Post-Sync Commands for certificate management!
After a certificate is deployed through your Infisical Gateway, you can automatically run commands on the destination server, like reloading NGINX or binding the certificate to a port in IIS.
See it in action 👇
Daniel retweeted
Agents shouldn't see your secrets.
Today, most deployments hand the agent a real API key and hope for the best.
That's why we're launching Infisical Agent Proxy.
You give an agent a fake API key. The agent uses that key and the proxy swaps it for the real one at the network boundary before forwarding it outbound to its destination.
An agent can't leak a secret it never sees. Build and deploy AI agents securely with Infisical Agent Proxy.
Daniel retweeted
Today we're launching Infisical PAM.
Privileged access has a reputation: something security deploys and developers avoid. Usually because getting access means pinging an admin and waiting.
With Infisical PAM: open the dashboard, find the production database, hit launch.
You're in a SQL editor, connected to production. No password, nothing to copy, and no one to ping. We record the session, access expires, and you go back to work.
our ceo is gonna see this and start pushing straight to main
i've never been a professional software engineer. fable has helped me to write production code that a mid-senior level swe might write.
with opus, I felt comfortable making basic frontend changes, editing copy, deleting a column in the UI here and there.
with fable, i'm making backend changes that our eng team is somewhat impressed by. its crazy how much this changes the world of building software.
