Twitxy Saved

Michael Grinich

Verified account WorkOS

@grinich

@WorkOS founder
workos.com Joined October 2008
329 Following 16K Followers 12K Posts

Latest posts 5

Michael Grinich Verified account @grinich
An update on the WorkOS security incident:

Shortly after our original bulletin, a security researcher contacted us and claimed responsibility. They told us they were evaluating ARTEX, an autonomous penetration testing framework, when their agent escaped its isolated testing environment and interacted with WorkOS unintentionally.

We asked for technical evidence. The researcher provided request details, timestamps, and artifacts from the activity. Our security team and an independent forensic investigator matched that evidence against our logs, establishing with high confidence that this individual was responsible for the unauthorized activity we observed.

The researcher has confirmed that all WorkOS data obtained by their agent has been deleted and was not shared with anyone else.

Their explanation that the activity was unintended does not change how seriously we take the incident or our responsibility to our customers.

Full report: workos.com/security/bulle…
51 replies 18 reposts 360 likes 83K views View on X
Michael Grinich Verified account @grinich
DX -> AX
Kenneth Auchenberg 🛠 Verified account @auchenberg 3d
For a long time I’ve talked about Agent Experience. Many think AX is the new DX, but that misses the bigger picture.

We’re moving to an agent-first world, where agents are the primary users of all software.

AX isn’t just the new DX. It’s the new UX.

innovationendeavors.com/insights/ax-is…
View quoted post on X
4 replies 0 reposts 7 likes 1.6K views View on X
Michael Grinich Verified account @grinich
Security “pre-releases” for critical vulnerabilities are becoming more common, giving many days advance notice.

How should companies prepare for this? Set a calendar reminder? Create an incident? Auto-merge the package when it drops?

Every minute will matter. The threat model has evolved. Agents move at machine speed.

The speed of your CI may be the time interval you remain vulnerable.
Node.js Verified account @nodejs 4d
Security release pre-alert:

We will release new versions of Node.js 22, 24, and 26 release lines on or shortly, after 2026-11-11 in order to address security vulnerabilities.

The highest severity issue fixed in this release is HIGH.
nodejs.org/en/blog/vulner…
View quoted post on X