building @infertrail and memes. someone's using your llm keys and it's not you. i catch that.

Joined February 2014
Your inference may already be getting resold — and your logs can still look normal. If you run an inference API, gateway, or AI product and you’ve seen suspicious credential sharing, resale, or unexplained usage, DM me. I’m looking to talk to teams seeing this in production. There is a growing reseller market built around stolen API keys, shared subscriptions, proxy access, account farms, and piggybacked sessions. The scary part: much of it can look completely legitimate from the provider side. Valid credential. Valid account. Normal-looking requests. Meanwhile, the same access can be passed through brokers, resold across borders, or quietly used by someone the account owner has never heard of. Most LLM security products focus on what an agent is doing. The blind spot is who is actually behind the account. That’s what we’re building at @infertrail: behavioral detection for inference abuse, credential resale, and unauthorized access. We’re publishing honeypot data, reseller-market research across Russian- and Chinese-language communities, attack patterns, and what we learn building detection for this problem. Follow @infertrail for the research.
9
1
171
20,532
As if we didn’t have enough 0days already
ah yes, of course there's another one today
1
6
470
Ah yes even more terrifying news lol
There is an (unpatchable?) supply-chain zero-day in PyTorch autograd that allows a regularization term to use the model's weights as RAM and SGD as its CPU clock to run any computation during training.
1
249
i just saw this. weird no?
5
272
PHP and SSL CA's being broken in the same week... It's like finding out all building foundations are fucked
1
112
Distillation is bad for us because reasons
76
we are living in a brave new world of infosec
In the last 24 hours: 1. iPhone 11 through 16 are apparently vulnerable to remote attacks. 2. SSL certificates are broken until browsers remove eMudhra CA. 3. PHP >9 vulnerability CVE published (tomorrow). The world is about to witness things that have never been seen before.
Readers added context they thought people might want to know
The post's iPhone claim is inaccurate; a leaked Cellebrite forensic tool targets a Bluetooth bug patched in iOS 26.5 and does not affect updated devices. The eMudhra CA and PHP issues are real incidents but framed sensationally. justin.sh/blog/2026/10/c… blog.mozilla.org/security/2026/… php.net
2
68
apparently we have node2shell today as well????
142
summary of eMudhra situation
47
so we don't even have a true patch to the most consequential 0 day of 2026. we are so screwed
Leaving this here, PHP 8.5.12 security patch is incomplete. ( needs further validation )
Readers added context they thought people might want to know
The PHP 8.5.12 release fixes the two specific CVEs (via state/bailout changes) detailed in official advisories; referenced "surviving paths" (e.g. var_destroy UAF) are separate pre-existing unserialize issues unrelated to this patch. php.net/archive/2026.p… github.com/php/php-src/se… github.com/php/php-src/se… github.com/dinosn/php-8.5…
1
3
209
this is why trust is so important in software. if you can't trust a scanner then it degrades trust in all your other cyber products even if they are internal
Bunch of emails (including large customers) saying we are impacted by the php vulns, based on vibe coded scanners released overnight. We do not use php, and this is hell.
3
183
did they time this to go down the same time that PHP and SSL cert apocalypse happened lol
We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks githubstatus.com/incidents/n…
1
183
With the recent disclosures of php2shell, litellm breach and the eMuhdra’s SSL compromise it’s becoming more and more clear how cybersecurity is going to become a big issue for software developers and can no longer be thought of as an afterthought. Attacks are becoming more and more frequent and what companies now need more than ever is to detect breaches as fast as possible and patch asap. At InferTrail we’ve been seeing this a lot with inference abuse at scale. We are committed to helping companies close these gaps wrt to inference theft and stop companies from losing money with fraud abuse and more. These operations aren’t fly by night they are serious operations that are not just in China or Russia but all around the world.
87
the boring prep that helps when the next critical vuln drops: know which services run what keep runtimes supported make sure your WAF can’t be bypassed keep internal tools off the public internet limit what a compromised worker can access practice patching every replica ‘we patched the host but missed the containers’ is an avoidable incident. Stay safe out their folks
The Cloudflare's writeup on our php2shell response is up. Rules went live at 03:02 UTC, about 9 hours before disclosure. Unfortunately the vulnerability leaked early, so we were already watching attackers mutate payloads against the rules and updating as variants appeared. New rules keep landing in the WAF changelog. Expect updates through out the day. We will have a more thorough post of what we had to build to better protect people coming shortly. PHP runs almost 70% of websites. The flaw is in the runtime, so updating plugins won't fix it. Patch PHP. blog.cloudflare.com/php-vuln…
2
3
203
Here we go again lol. They should literally just call GitHub Actions GitHub Degradations
We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks githubstatus.com/incidents/n…
50
I wonder if the NSA uses a lot of PHP
Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.
1
1
2
318
Gonna say it this is one of the least clandestine operations in history. KSA is basically admitting they funded the guy by offering to cover his bail
‼️ Saudi Arabia offered to cover a $1M bond for the OpenAI engineer accused of bugging an exec meeting room. The judge said no. Prosecutors say the LA consulate behind the offer helped a Twitter employee later charged as a Saudi agent catch a next-day flight home in 2015 💀
1
122
I've been seeing this a lot in my own security research at InferTrail. We are seeing increase in attacks to steal their inference. This is unfortunately not going to stop its going to get worse.
Replying to @JFrogSecurity
🔎 We break down the LiteLLM hijacking, the attack details, and what you need to know in our blog 👇 research.jfrog.com/post/lite…
46
Turns out if you convince enough people you can just become CA without ever doing due diligence.
1
120