cookiengineer
Would love to take a look at it.
[1] https://github.com/cookiengineer/check-claude-code-exfil
In all seriousness, there is nobody at Anthropic who can even give you that answer, because nobody there reads their pushed code anymore. Take a look at the previous Claude Code leaked codebases if you don't believe me, there is hundreds of files with 1000+ or more import statements at the top.
Any human would immediately tell you that it needs to be refactored from scratch. Their codebase also leaked that they're using review bots automatically instead of a human-in-the-loop review process.
[1] https://m.youtube.com/watch?v=3TNpOD6bov8
edit: downvoting me doesn't make it untrue, by the way. Check the leaked codebases, I dare you to provide evidence to the contrary.
Hello, blast from the past! Feels like a lifetime ago.
I'm so grateful for WHATWG listening to the jquery community though, sizzle.js and the CSS query selector API made building dynamic websites so much easier.
Just for context, that is the type of evil we're talking about here.
A German comedian made an episode about it [1]
The tutorials and hands on coding examples made me understand how to program with GPUs. I loved them because at the time, khronos was still in its infancy and just started out with GLES extensions and the whole WebGL ecosystem.
Meanwhile I kind of believe that learning where it came from (fixed function pipeline, buffer/texture and uniform problems etc) makes a lot of sense to learn first so you start thinking in shader computation pipelines much easier, as you understand the whys and whens much better.
Tricks for obfuscation I learned over the years:
- use exfil protocols (e.g. http smuggling via chunked encoding, DNS TXT)
- rotate exit nodes while sessions not only between (ronin behavior)
- encryption is useless with no padding or zero based padding, use one based padding instead
- scatter traffic through peers
- use manual caching everywhere, DNS TTL, HTTP entity based tracking, etc will be automatically unfeasible
- always think about the god's eye perspective of ISPs
One of my working soft router concepts, I've open sourced as Tholian Warps [1]
Where are all those folks now?
For reference (the thread I am talking about): https://news.ycombinator.com/item?id=50219177
If yes, check for [1]
Read up on what ASLR does, then read the heap feng shui document, then come back here.
Because it does not work the way you think it does.
So many wiseasses here with zero knowledge about exploitation, it's getting ridiculous.
I even let the agent create two separate demos for this, one for ASLR and one without, but people are still to stupid to understand it.
Versions are pinned, replace it, check the fatal.php to get the initial memory distances, then retry it again. It'll work, that is the freakin point of the demo.
Read the heap feng shui doc, and headline 4 in the README.
The involved heap feng shui is independent of ASLR.
Maybe read up on what ASLR actually does before trying to be a wiseass?
It is split up into two branches and demos, see the heap feng shui document?
ASLR enabled requires a way to create more data, which I intentionally did not create in the index.php because other folks claimed that is "cheating". That was the demo that wiz created.
Maybe you should read the repo next time? It is literally headline 4.
The whole point of this demo is that the assumed to be hard part (mem feng shui) is what LLMs are actually good at.
The only thing you have to know in advance is the relative memory offset distances, and that's it. Memory feng shui was the longest part of the implementation.
No I proved exactly that. Learn to read.
No, I did. But thanks for leading with an offensive comment, makes reading the rest much more enjoyable /s
> Take a look at the php files you're shipping with your "stock" server - theyre pretty contrived, no? fatal.php? producer.php boom() str repeat X 32?
> You use that to get the constants for the RCE, but without that information you're in trouble. How transferrable are these constants? Do they work with any config changes?
Yes, they work with changes. The point is that you have to use a container to have a reproducible memory layout that you can target. And that _is_ known and _is_ reproducible.
It's not that hard to find out which OS images or which PHP version you're running on the server, there's plenty of well working scanning tools (e.g. projectdiscovery).
And this is setting aside that 99% of servers probably run standard versions of Ubuntu or Debian combined with the distribution packages of Magento, Wordpress, etc. And those are also reproducible in their memory layout, hosting setup, built package versions, etc.
Just as a disclaimer because I know where this is going: No, I didn't target muslc. Because most operating systems still don't use it, and that's the actual problem here we should discuss here.
https://news.ycombinator.com/item?id=50195017
Vibecoded on purpose without any of my influence, just to prove a point that a local Qwen3.8 model that's post trained on DeepSeek's reasoning traces makes this exploit and the necessary Heap Feng Shui totally feasible.
Here we go, 12 hours later, end-to-end exploit of an index.php that echoes "ok" and nothing more. Pinned PHP versions, reproducible containers for each of the CVE and exploit path/killchain variants and everything.
php.ini set intentionally to defaults. max_input_vars set to defaulted value of 1000 so it's actually harder to exploit than with a higher value.
Implemented using my Exocomp agentic environment, and my post-trained Qwen3.8 27B model that I trained on reasoning traces of DeepSeek v4 Pro. All on my github, needs a single 48GB Radeon VRAM GPU for training/inference via Vulkan (before someone claims it's too expensive).
Wake up folks, your assumptions about what is hard to do and what is not is the wrong rationality here. Humans are sequential beings, therefore we think that a lot of tasks are harder to achieve. But that's not the correct metric.
Heap Feng Shui work is gruntwork, therefore LLMs are better and faster at this than any human could ever be.
Re: Hours later – No, there is an easy way to exploit this vulnerability
Fixed that for you
He might also still be using SunOS or HP/UX or maybe even 386BSD.
But is that likely? Not being pwned/hacked for 25+ years while still using the same old OS? On the internet that changed quite a bit since HTTP/0.9? While using the GitHub website with TLS and HTML5 and JS requirements to register an account which doesn't run in such an outdated browser?
I think your assumptions about statistical likeliness are a bit off.
There's enough demo videos on how to use gogs, github or forgejo on YouTube.
I have faith in your ability to use the YouTube search.
I criticized the intentional creation of a GitHub account just to write a README file wherein they say that there's no repository, instead of providing any useful information for people looking for a repository.
If there's no repository and you go to such great lengths just to clarify that there isn't any, then maybe you can just push your code to codeberg or gitlab or a selfhosted gogs instance if you don't trust them?
Nobody said that he MUST accept pull requests or MUST engage with any community at all. You can just disable all the features, I do that too since 4chan raided my repos in 2021 and GitHub didn't do shit about it.
But this way at least there's no risk for people installing malware infiltrated forks of xscreensaver on their machines. And that's what is the important part that wasn't actually solved/avoided/prevented with that README file.
Setting up a git mirror that auto syncs takes less than 2mins of effort. And way less time than writing up this README that's just there to lecture people. If it's about disagreement with github, there's also better alternatives.
You can still setup the mirror and be done with it, and put the original repo links at the top in the README.
Ghislaine Maxwell's social security number?