Moonbound Update: Reset, Security, and What Comes Next
First, responsibility where it belongs.
An insider incident occurred involving a former developer who inserted malicious logic into a Moonbound token contract template prior to mainnet deployment. This was not a hack, not a protocol failure, and not a user security issue, but it was unacceptable, and it’s on us to address it fully and transparently.
We did.
What this means for existing Moonbound tokens
Because the affected contracts are immutable, all tokens launched under the previous Moonbound deployment will no longer be supported by Moonbound going forward.
While only a small number of tokens were actively impacted, all tokens launched from that contract template technically share the same latent risk profile. For clarity, safety, and fairness, there is no partial solution here.
A clean reset is the correct move.
This is not a judgment on token creators or communities, it’s a necessary step to ensure Moonbound moves forward on uncompromised ground. We'll be excited to support any token creators/projects that are interested in re-deploying.
The reset: what’s changing technically
Moonbound is being redeployed on Kasplex L2 in a fresh, clean environment, using contracts that have been fully corrected and hardened.
Specifically:
- The malicious logic inserted by the former developer has been completely removed
- Contracts have been reviewed line by line
- All logic has been revalidated for full consistency with the Hexens audit
- Hardcoded values, privileged paths, and edge cases have been systematically eliminated
- Repository access and review processes have been permanently tightened
This redeployment is not a patch, it’s a proper reset done the right way.
Why Moonbound is secure going forward
This incident required insider access and intentionally malicious code. It is not something an external actor could reproduce.
With the new deployment:
- There is no privileged transfer logic
- There is no hidden mint or balance bypass path
- There are stronger review and monitoring controls
- There is clearer operational separation between contributors and deployment authority
Moonbound is launching forward from a known-good, audited, and verifiably clean baseline.
What’s next: Moonbound expands
This reset also creates space to move faster and bigger.
We’re excited to introduce Moonbound as a multi-network launch platform.
- Kasplex L2 redeployment is the immediate next step
- Igra Testnet support is coming soon
- Igra Mainnet support will follow as soon as the network is available
Moonbound’s goal remains the same: fair, transparent, and permissionless token launches — now with a broader network footprint and stronger foundations.
Final thoughts
This situation was serious. We treated it that way.
We investigated thoroughly, preserved evidence, removed the bad actor, reported the incident along with evidence, corrected the system, and chose the harder but correct path forward instead of a partial fix.
Moonbound isn’t retreating, it’s resetting with intention.
Thank you to everyone who stayed patient, asked hard questions, and held us to a high standard. That accountability makes the platform stronger.
More details soon as redeployment progresses.