(6/6)
It’s built for authorized security research, education and testing on systems you own or have explicit permission to assess.
It’s dual-use tooling, so please use it responsibly.
P.S.: Don't forget to use Uncensored LLMs 🤫
(1/6)
Hey #CyberSecurity folks & #SecurityResearchers,
I just open-sourced ShellCoder, a fully #LocalLLM assistant for Offensive Security research (Specially for #ExploitDevelopment). 🤷♂️
MIT licensed. Feedback, issues and PRs are very welcome 👇
https://t.co/yS02Ud40M6
(5/6)
The idea: ask questions against your own research, like “What’s the SEH offset mentioned in that PDF?”, without pasting it into a third-party service.
Crazy 72 hours in security. Three major incidents dropped back-to-back: eMudhra, PingCAP (TiDB Cloud), and PHP.
Here is the short version of what happened and who got hit.
1. eMudhra (Trusted CA compromise)
eMudhra generated 8 intermediate CA certificates in April 2025 (cross-signed by Sectigo). A bug in their HSM key-wrapping test script created a second set of P-384 keys where the private keys were single-byte numbers under 256. Operators picked the wrong key labels and signed them into real CA certs.
One of the intermediate CA private keys was literally the number 4.
The other seven: 56, 66, 115, 155, 156, 230, 237.
Three weeks later (May 2025), their CRL signatures started failing because the CRL signer was using the real keys instead of the weak ones. Instead of asking why the keys didn't match, someone switched the CRL signer to the weak keys and closed the ticket.
• Browsers are safe: Chrome, Firefox, Apple, and Microsoft already blocked them, and zero rogue certs hit CT logs.
• Servers are not: curl, Python (certifi), Go binaries, and Docker base images don't check CRLs. Update ca-certificates, certifi, and Go (1.27.3 / 1.26.10).
• 10-second check on any server:
curl https://t.co/vhiGLxNhIS
(TLS error = safe. 200 OK = still vulnerable.)
2. PingCAP / TiDB Cloud (10.6 TB breach)
Attackers found GCP and Azure credentials committed inside PingCAP's own repos. They set up a replication feed of TiDB Cloud's production control plane and exported the entire database every 6 hours for 22 straight days. 88 full exports, zero alerts. 200 GB is already out on torrents.
Beyond the 413 private repos and 20.6M customer SQL queries logged from their web SQL Editor, PingCAP engineers were pasting customer secrets into Jira tickets.
Who is affected in the leaked records:
• Live credentials exposed in support tickets:
- Pinterest: AWS keys for their pingcap-logs S3 bucket
- CardX / Silverlake (NPCI-linked env): AWS admin key in a backup log with full access to 258 external S3 buckets
- DeBank: 38 presigned S3 URLs
- An unnamed AI/dev platform: a 314 MB slow-query log attached to a ticket containing 8,027 live customer secrets (an AWS root key, a GitHub admin PAT over 1,701 repos, 7,485 AWS STS tokens, and 192 OpenAI/Anthropic/Gemini keys)
• Tenants with infra metadata, VPC CIDRs, app-server IPs, or contract pricing exposed:
- Tech: Atlassian, Databricks, Airbnb, Baidu, LINE, Nylas, Persona, PatSnap
- E-comm & Travel: https://t.co/C512KFOEq5, Shopee, Flipkart, Mercari, ZOZO, AEON, Delhivery, Klook
- Gaming: Capcom, Square Enix, Konami, Bandai Namco, Cygames, Colopl, DMM
- Finance: PayPay, SoftBank, SBI, SB Payment Service, Fujitsu, TOPPAN, Bank of China, China Life
- Crypto: Bitget (said only public trade logs were on it and they already left), Pionex, DigiPlus, NFTscan, Chainbase
• Developer profiles leaked (from a purchased https://t.co/28tjHqd5Wr table in PingCAP's BigQuery):
- 24,900 personal emails + GitHub/LinkedIn profiles of engineers at Tencent (3,327), Huawei (2,726), ByteDance (2,475), AIG (2,140), Mastercard, Flipkart, and bKash.
If you use TiDB Cloud: rotate your console API keys, DB passwords, and anything you ever pasted into a support ticket.
3. PHP "PHP2Shell" (CVE-2026-109618 & CVE-2026-109619)
Two CVSS 9.2 pre-auth RCEs leaked yesterday ahead of today's 14:00 UTC patch.
Public writeups trace it to a heap Use-After-Free in PHP's native C multipart/form-data session upload-progress handler (ext/session/session.c).
Because C-level multipart parsing runs before line 1 of index.php:
• App auth, Laravel/WordPress middleware, and file_uploads = Off do not stop it.
• Only PHP 8.2–8.5 get official patches today (59% of PHP servers on Shodan are on EOL <= 8.1).
• Until you patch php-fpm: lock php_admin_flag[session.upload_progress.enabled] = off and block unexpected multipart requests at Nginx/Apache/Cloudflare.
FDIE by Magdox is finished: firmware and source code security in one app for IP cameras, routers and gateways.
Every component, known exploited vulnerabilities first, every release compared.
Try it, no sign-up: https://t.co/rrzjB2lcWJ
We tried retiring ShellOrbit's free plan last week. You told us that was a mistake, and you were right.
The free plan is back for everyone: 15,000 webhook events a month, 15 days of history and replay, no card required.
#webhooks#developers#saas
(4/4)
Every finding shows its evidence, what was covered, and what a reviewer decided.
Exports in SARIF, CycloneDX and SPDX.
If you run AppSec and want to shape it: https://t.co/GPJ4OENSAv
(3/4)
The magdox CLI runs on your machines and in CI (Windows, macOS, Linux).
It scans code, dependencies, secrets and config locally. Only findings go to the dashboard.
Code snippets are off by default.
Side project, now live. #devtools
Every deploy has a few seconds where the server just isn't there. #Webhooks don't care about your deploy window.
Neither do I, apparently.
This catches them anyway. So here you have https://t.co/uYeJzZH3WT
It has paid plans because of AWS 😔.
Q: How do you actually verify the fix is complete at the #binary level? Or are we taking #release notes at face value? Under #CRA timelines, a vendor "pinky-promise" won't hold up in court.
P.S. I let AI generate the image. Don't look closely at the metadata! 😜 (5/5)
They didn't fix the #vulnerability. They just gave it a fake mustache. 🥸 (yeah just like that)
Unless you use advanced binary analysis tools, very few internal teams have the time to systematically verify whether a vendor's patch "actually" eliminated the bad code. (4/5)
Tbh I think if someone fr wants to learn malware development you shouldn't even begin studying malware techniques
You should focus on things that interact with the OS, like file creation (and all the silly quirks of it on Windows), working with the registry, file system enumeration, basic networking stuff (WinHTTP vs WinInet vs WinSocks vs IpHelper).
Having a good understanding of these will make life a lot easier
Then when you feel really really comfortable and do silly stuff like that, then slowly introduce some malware stuff because a lot of malware stuff is just abusing the concepts described above
Also probably explore the Windows API and all the weird shit inside of it that isn't documented well. I also recommend reviewing ReactOS source code to get an understanding of what's going on under the hood
ReactOS isn't 1-1, but it's close enough