> For the complete documentation index, see [llms.txt](https://ir0nstone.gitbook.io/notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ir0nstone.gitbook.io/notes/binexp/heap/the-malloc-maleficarum.md). # The Malloc Maleficarum The first heap exploits In 2001, two of the most famous heap exploitation papers were printed in the famous [Phrack](http://phrack.org) magazine - [Vudo malloc tricks](http://phrack.org/issues/57/8.html) and [Once upon a free()](http://phrack.org/issues/57/9.html). These are some of the very first heap exploitation techniques published, covering some of the ones you have read about previously. In late 2004, glibc was hardened, and this rendered these exploits obsolete. The next famous heap exploitation paper was [The Malloc Maleficarum](https://seclists.org/bugtraq/2005/Oct/118) in 2005, which documents a collection of techniques sorted into *Houses*: * The House of Prime * The House of Mind * The House of Force * The House of Lore * The House of Spirit * The House of Chaos Each of these had its own unique spin. In keeping with this tradition, modern heap exploits are often nicknamed as their own *House*, such as the [House of Rust](https://c4ebt.github.io/2021/01/22/House-of-Rust.html). The original houses are the cornerstone of modern heap exploitation, and while they're no longer possible, they were until more recently that you'd think. They are also important to understand to build up your knowledge. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://ir0nstone.gitbook.io/notes/binexp/heap/the-malloc-maleficarum.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.