Techster | helius.dev

Product Design & AI @helius | Member of @SuperteamBLKN Designer. Investor. DeFi Enjoyor. Aspiring Biohacker. Ex. @binance

[Orb @Orb_Markets]

Lana is now on X.

Tag @lanaAI_bot in a reply to any post and ask about the transaction, wallet, or token in it. Lana reads the post and answers in the thread.

Here it explains a tx from just a link, then traces who funded the wallet behind it.

[Techster | helius.dev @Techster]

@Helius Massive unlock for Solami products

[Helius @Helius]

Introducing the Parsed Events Scan API

Find the transactions you need in any Solana address’s history, already parsed, 10x faster and 30x cheaper

Filter by named program instructions, discriminator prefix, token mint address, native SOL, or any combination of filters

[Techster | helius.dev @Techster]

@KeystoneWallet Better comms on UI pls in the future

[Techster | helius.dev @Techster]

@KeystoneWallet Thanks

[Marcus Hutchins @MalwareTechBlog]

I'll be the first to admit I'm mediocre at exploit development, but I am in contact with enough extremely talented exploit developers to say this for certain:

Anyone claiming they were "easily" able to generate a working php2shell exploit with AI is either:

a) a world-class exploit developer with an extreme case of imposter syndrome.

b) currently looking at some very confident-sounding but wrong LLM output.

I'm rather certain it's the latter based on the number of AI-hallucinated exploits I've seen posted on GitHub. Threat actors are also blasting my honeypot network with "php2shell" exploits that not only don't work, but aren't even within 10,000 miles of anything to do with how the exploit actually works.

I've seen the same technique from the attached image in multiple alleged "php2shell exploits", including one on GitHub with over 100 stars. Problem is, it's not php2shell, nor is it even a vulnerability at all. It's a technique known as "session poisoning", which can be leveraged to exploit local file inclusion (LFI) vulnerabilities in PHP apps (not PHP itself).

The only thing it has in common with CVE-2026-109618/CVE-2026-109619 is they both use the "PHP_SESSION_UPLOAD_PROGRESS" feature. And mitigation advice for both issues reference setting "session.upload_progress.enabled" to "Off".

People are shoving loose details of the vulnerability into LLMs, the LLMs are keying in on the "PHP_SESSION_UPLOAD_PROGRESS" string, then generating session poisoning code that has nothing to do with the actual CVE. And because the people doing this have absolutely no idea what they're doing, they're confident enough to post their "proof of concept exploit" to GitHub and share it on social media.

So if you see people talking about "session poisoning + LFI" it's likely their LLM hallucinated an exploit based on a 2018 blog by Orange Tsai talking about a local file inclusion attack vector.

What's even worse is that "security researchers" are then using LLMs to triage these exploitation attempts, falling victim to the same hallucinations, then confirming there is ongoing mass-exploitation (there currently isn't).

The actual real exploit is very difficult to exploit, and so far I've not seen anyone successfully get it working on more than a handful of PHP version with highly-specific configurations.

LLMs are useful tools in the hands of skilled professionals, but for others, they're often just a Dunning-Kruger accelerator.

[⁵⁄₉ @fiveoutofnine]

So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and https://t.co/QlOXb3COq3 went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.

[toly 🇺🇸 @toly]

.@jacobvcreech remove the beta tag in the explorer

[Techster | helius.dev @Techster]

@hylo_so Barry?

[Orb @Orb_Markets]

Know your rights.

@solana is becoming the home of tokenized stocks, and Orb is built to help you navigate them.

One stock can have many versions. See what each one represents, what rights it gives you, and how redemption works.

[Helius @Helius]

Preconfs are now live for all paid plans

Use preconfSubscribe to stream the earliest onchain signals and see Solana transactions before they're shredded

We also added 4 new filters: source (Helius/BAM), signer (include/exclude), signatures, and instructions

Have fun

[Orb @Orb_Markets]

Less clicking, more context.

New token cards put price, 24h chart, market cap, and volume one hover away on any transaction or account page.

[Techster | helius.dev @Techster]

@superteam @Helius @solana @SuperteamBlack This is how entry barriers are destroyed

[Techster | helius.dev @Techster]

Obviously biased but,

Helius literally wants you to win.

[Superteam @superteam]

building on solana just got a little easier 🛠️

we’ve teamed up with @helius to give superteam members access to exclusive developer infrastructure perks.

here’s what’s available ↓

[Techster | helius.dev @Techster]

Talk to the chain (fast)

[Guney @guneysol]

you can ask lana what any solana wallet has been doing

it’s now smarter and 40% faster

[Techster | helius.dev @Techster]

@guneysol Wow

[Techster | helius.dev @Techster]

CT is overwhelmingly bearish, would be a shame if...

[Techster | helius.dev @Techster]

@superteam Massive win for us over at Helium

[Techster | helius.dev @Techster]

shopping time complete

[Techster | helius.dev @Techster]

shopping time.