Madium
Free on Windows, and that is the whole pitch. Madium hands over what the paid tools charge for, and takes its cost elsewhere: a ban wave in the trackers' records, and sources that cannot agree on whether it asks for a key.
Windows Free
Madium charges nothing. That is not the same as costing
nothing: the trackers list it as detected and keep a ban wave in their
records. Several domains wear the name, and its own documentation names
getmadium.online as the official one. The file we host is our
own copy, tested and scanned before it went up. No step of the install
needs your Roblox password or your card details.
At a glance
| Detail | Madium |
|---|---|
| Platform | Windows 10 or 11, 64-bit |
| Price | Free |
| Language | Lua / Luau |
| Latest version recorded | 2.4.7 |
| Key system | Yes, according to ScriptBlox |
| Reported UNC | 98%, from a secondary source |
| Reported sUNC | 100% |
| Decompiler | Yes |
| Multi-instance | Yes |
| Ban risk | Yes |
| File checked | Yes, tested and virus-scanned |
Screenshots
Pick one to see it at full size.
What it is
Olemad develops it, the documentation lives in a public repository, and the
name breaks the habit of the rest: the others here take theirs from elements,
and Madium is branding. The application attaches to Roblox's client and runs
Lua and Luau code inside a game while you play, outside the
flow the game intended. Its own documentation names
getmadium.online as the official domain, which matters because
several others answer to the same name.
The price is where it separates from its neighbours. Wave, Volt and Potassium charge by the week or the lifetime, and Madium hands out the same kind of thing for nothing: a decompiler, several Roblox instances at once, a modern API and an editor of its own.
What it asks in return is quieter than a price tag: ScriptBlox records a ban wave in May 2026, and the directories cannot agree on details as basic as whether the build asks for a key.
What it can do
The game and the script decide between them, and it helps if the two were made for each other. The headings below are the ones scripts tend to fall into:
Visual and environment changes
- The skybox, the fog, the lighting and the field of view, all changed locally.
- ESP: where players and objects are, and how far, with markers over the game.
- Overlays and HUDs you draw yourself, plus chams, fullbright and the fog removed.
- Replace textures or models locally.
- Free cameras and visual effects.
Automation
- Auto-farm, with Blox Fruits and Pet Simulator as the usual targets.
- Auto-clickers and macros, with conditional logic.
- Movement bots and local teleports.
- Aim assistance, where a script provides it.
- Auto-execute, which starts a script the moment the injector attaches.
Interacting with the game
- Play animations, sounds and effects.
- Change the client's own interface.
- Simulate input: keyboard, mouse, taps.
- Intercept the game's own calls and change what they do, locally.
Advanced scripting
- Load script hubs (Rayfield, Fluent, Kavo, Orion).
- Lay out menus and windows of your own, drawn by the game.
- Draw overlays with the drawing API.
- Let scripts talk to each other through
getgenv(). - Read and write files, to keep a configuration between sessions.
- Encode and decode scripts with the built-in cryptography.
- Inspect the running environment: objects, functions and the stack.
- Talk over a socket, with the network functions it exposes.
None of these are necessarily built into Madium: they depend on the script you run.
Requirements
| Component | Detail |
|---|---|
| Operating system | Windows 10 or 11, 64-bit |
| Processor | Any modern x64 |
| Memory | 8 GB recommended |
| .NET | Framework 4.8 or newer |
| Permissions | Administrator rights, because it handles processes |
| Roblox | The current version |
| Antivirus | One exclusion is normal here. The technique the injector uses reads as suspicious to a scanner; the file we host has been scanned already. |
| Licence | Free, but ScriptBlox records a key system, and that is a step and a link to get through |
Download Madium
Windows only, and our gate stands between the button and the file. The warning above is short, and the two lines in it that matter are the ban wave and the key.
How easy it is to use
- Installing it is simple: download it, run it as administrator, attach it to Roblox, plus the extra step of whatever the key system asks for, if the build has one.
- The interface is modern and clean: an editor that keeps several scripts in tabs, with syntax highlighting and partial autocompletion, and a console.
- Running scripts somebody else wrote is very easy, and writing your own is medium, since that needs Luau. The advanced parts, hooks and metatables, are hard, and they are where its documentation is strongest.
- Getting started is covered by its own documentation and the guides in its Discord, which is more than the older free executors offer.
- When something goes wrong there is a console with the error, the logs and how long the script ran, plus the debugging functions for looking inside a running script.
Community
It is newer and smaller than the paid ones it competes with, and younger than the other free executors here. That shows up in how much has been written for it specifically:
- An official Discord, which is also where support happens.
- YouTube, for demos, tutorials and script reviews.
-
Reddit, in
r/robloxexploitsandr/robloxhackers, including the threads that question whether it is safe. - GitHub, where scripts and interface libraries live, though the executor itself is not there.
- Exploit forums, where the older threads on it live.
That community keeps turning out hubs, libraries and interfaces, and shares configurations for each game as a matter of course.
Strengths and weaknesses
What it does well
- It is free, and the decompiler, the multiple instances and the modern API are the things the paid executors charge for.
- A modern, complete API, compatible with the scripts written for Synapse X.
- Debugging functions that go further than most: the stack, the info of a function, its upvalues and its constants.
- Cryptography built in: base64, sha1, md5 and hmac.
- A clean, well organised interface, with tabs for your scripts.
- Network functions, including sockets.
- A filesystem, so scripts can keep a configuration.
- Fast recovery after a Hyperion patch, when it goes well.
- Support from the team, in their Discord.
Where it falls short
- Its detection record. ScriptBlox lists it as detected and records a ban wave in May 2026. That is the cost of the free price.
- Which download is the real one. There are several domains around Madium, and the official one they claim has not been verified here.
- A key system, according to ScriptBlox, which the directories disagree about.
- Windows only.
- A smaller community than the established executors have.
- Less known, so fewer scripts are written for it specifically.
- Its usefulness depends on the bypass: a drastic change to Hyperion can leave it unusable for a while.
- The advanced parts take time to learn: hooks and metatables are the steepest.
Hubs, libraries and extras
No plugin system, then. What surrounds it is an ecosystem of its own, arranged like this:
Script hubs: a whole interface, ready to use
- Rayfield UI, the one most scripts use.
- Fluent, which looks like Windows 11.
- Kavo UI, minimal.
- Orion, modern and modular.
- Obsidian, for the more complex interfaces.
- Linoria, for advanced menus.
Support libraries
- WindUI, Lunar and Fatality, among others.
What comes built in
- Auto-execute when it attaches.
- A scripts folder, with some organisation.
- An editor with syntax highlighting, in tabs.
- A console with live output.
- Several scripts at once, in tabs.
- Save and load the ones you use.
- A filesystem the script can write to, and read again in the next session.
- Cryptography, to obfuscate a script or decode one.
Compatibility
- High with the Synapse X API, so many older scripts still run.
loadstring(), for scripts kept at a URL.- External modules through
require(). - Most scripts written for Wave, Potassium and Volt work in it.
Madium, Wave, Volt, Potassium and Xeno
Side by side, with the prices and the compatibility figures the vendors and the directories announce rather than tests run here:
| Feature | Madium | Wave | Volt | Potassium | Xeno |
|---|---|---|---|---|---|
| Price | Free | $4.99 a week | $5.99 a week | $22.99 lifetime | Free |
| Reported sUNC | 100% | 100% | 100% | 100% | Variable |
| Decompiler | Yes | Yes | Yes | Yes | Depends on the version |
| Multi-instance | Yes | Yes | Yes | Not confirmed | Not confirmed |
| Built-in AI | No | Yes | No | No | No |
| Detection risk | Yes | Yes | Yes | Yes | Yes |
Madium is the odd one out here by being free while doing what Wave, Volt and Potassium charge for: a decompiler, several instances and a modern API. The other free executor here, Xeno, is the opposite trade. It is older, more limited, and without the ban wave in its records, and neither of them is a safe download for the price of being free.
Status and safety as of 10 October 2026
Four things worth knowing first:
- Detection. ScriptBlox classifies Madium as detected and records a ban wave in May 2026. A reported sUNC of 100% means the scripting functions are implemented; it does not mean the tool is undetectable, and it does not mean it is free of anything else.
-
Which download is the real one. There are several domains
around Madium. The project's own documentation identifies
getmadium.onlineas its official domain; we link to it from nowhere, and the copy the download serves is the one we tested and scanned. - The version. The directories contradict each other about details as basic as the key system and the current build: 2.4.7 is what one lists, and another is still on an older one. Where they disagree, both claims are named and neither is chosen.
- What can change. Everything above can shift with a Roblox update, and some of it already has.
Download Madium
The button serves our own copy. Older builds, if you want one of those instead, are listed underneath.
Get Lua code for:
After Lua or Luau code for one particular game? Search the game's name: the page for it holds the codes its creator published, the tricks, and the guides for getting further. All of it free.
How it works
What Madium does differently once it is inside Roblox, and where the rest of the mechanism is written down.
Madium attaches to RobloxPlayerBeta.exe with the same toolkit as
the other Windows tools here: a DLL mapped without the Windows loader, a
thread taken over rather than created, hooks on the
NtReadVirtualMemory family, handles borrowed from another
process and a module kept out of the listing. None of that is its own, and
How an executor works takes it
apart once for every tool on the site. The layer above is where Madium
differs: each build carries its payload obfuscated, anti-tamper slows the
anti-cheat's inspection, and a repack follows the Roblox client when it
moves.
Memory access rests on a signed but vulnerable driver (BYOVD), borrowed rather than written for the job, so the door belongs to software the system already trusts. Nothing in that arrangement is fixed. A patch can close the driver or move the client far enough that the build stops attaching, and the tool then sits useless until someone rebuilds it. The status section above records how that has gone so far.
The API is the part the paid tools sell. Inside the client Madium exposes an extended Luau environment close to the Synapse X standard, with the familiar groups plus a few edges of its own: a filesystem, cryptography for encoding and decoding, and debugging calls that reach the stack, a function's upvalues and its constants. Multi-instance, auto-exec on attach and tabs for several scripts come with it.
| Category | Examples |
|---|---|
| Environment |
getgenv(), getrenv(), getreg(),
getgc(), getloadedmodules()
|
| Instances |
game, workspace,
Instance.new(), cloneref(),
compareinstances()
|
| Metatables |
getrawmetatable(), setreadonly(),
hookfunction(), hookmetamethod(),
getnamecallmethod()
|
| Network |
firetouchinterest(), fireproximityprompt(),
fireclickdetector()
|
| Execution |
loadstring(), require(), pcall(),
spawn(), defer()
|
| Utilities |
getconnections(), getsignal(),
checkcaller(), islclosure()
|
| Filesystem |
readfile(), writefile(),
listfiles(), isfile(),
delfile(), makefolder()
|
| Cryptography |
base64.encode(), base64.decode(),
sha1(), md5(), hmac()
|
| Debugging |
getstack(), getinfo(),
getupvalue(), setupvalue(),
getconstants()
|