March 12, 2026
Copycats with indemnity
Malus – Clean Room as a Service
Robots that “clean” open-source? Commenters shout satire, greed, and chaos
TLDR: A spoof-y site claims robot-written “clean room” rewrites let companies sidestep open‑source rules, sparking cheers, eye rolls, and ethics alarms. Commenters split between calling obvious satire and warning it’s a tempting playbook—proof that credit, licenses, and AI cloning are now everyone’s favorite internet fight.
The internet did a double take at “Malus,” a tongue‑in‑cheek site promising “Clean Room as a Service” where robots allegedly rewrite open‑source projects so companies can skip credit and obligations. The pitch? “Legally distinct code” and a zero‑attribution license, complete with cheeky fine print and a gag image. Commenters pounced: one asked if the motto is “Don’t be good?”, another mocked it as replacing your core tools with “unmaintained ripoff copies.” Several users yelled “this is satire,” pointing to the winking disclaimer and “offshore indemnification” gag on the site.
Still, the drama brewed fast. Some see a corporate fever dream made real: dodge thanks, dodge responsibility, profit. Others read it as a clever warning about how easily companies might try to skirt licenses like AGPL (a license that can force you to share your own code if you use certain software). And then there’s the chaos faction cheering, “Open the floodgates. Break the system.” The result is pure comment‑section theater: ethics vs. loopholes, parody vs. possibility. Whether Malus is a joke or a blueprint, the crowd agrees on one thing—if robots can “recreate” everything, the fight over who deserves credit just went from boring legalese to popcorn‑worthy spectacle.
Key Points
- •“Malus – Clean Room as a Service” claims to recreate open source projects using AI to produce legally distinct code with proprietary-friendly licensing.
- •The site highlights open source compliance burdens (Apache attribution, AGPL obligations, license tracking) as problems it aims to solve.
- •Process: upload dependency manifest; robots analyze only public documentation; a separate build team recreates functionally equivalent code without source exposure.
- •Output is delivered under a “MalusCorp-0 License” with no attribution, no copyleft, and no disclosure obligations, with claimed legal indemnification via an offshore subsidiary.
- •Example shows common dependencies (React, Lodash, Express) mapped to “m-” prefixed equivalents; dashboard shows zero projects processed and zero clients.