Malus.sh: How AI Clean-Room Clones Threaten the Open Source Sustainability Loop

Tue, 05 May 2026 07:16:47 +0800

What is Malus.sh

Malus.sh (pronounced like “malice”) is an AI-powered tool that claims to recreate functional equivalents of any open source software from scratch using “Clean Room” engineering methods, while stripping away all license obligations of the original project. Its most eye-catching slogan: “No attribution. No copyleft. No problems.”

What makes the project unique is that it is both a satirical work and a genuinely operating commercial product. Founder Mike Nolan works as a researcher on the political economy of open source at the United Nations. In an interview with 404 Media, he explicitly stated that if it were only satire, open source practitioners would dismiss it with “that can’t happen to me.” Making the tool actually usable forces the community to confront the structural cracks that already exist in the open source economic model.

Malus.sh is registered as an LLC, accepts payments via Stripe, and has real paying customers. Its “liberation service” is currently unavailable, but the industry discussion it ignited keeps spreading.

Technical mechanism: AI-accelerated clean-room engineering

Historical precedent of the traditional clean-room method

The legal foundation of clean-room engineering dates back to the 1982 IBM BIOS case. At the time, IBM monopolized the personal computer market, and competitors wanted compatibility without infringing copyright. The solution was:

Team A analyzes IBM’s original BIOS code and writes a functional specification
Firewall isolation: strict separation between Team A and Team B
Team B sees only the specification and reimplements the code from scratch
Legal outcome: functionally compatible but independently written code, ruled by the court to be non-infringing

This case was dramatized in the first season of the HBO series Halt and Catch Fire, becoming a key milestone in the history of software copyright law.

Malus’s AI version of the process

Malus fully automates the traditional clean-room method:

The concrete steps include:

Upload manifest: supports formats like package.json, requirements.txt, and Cargo.toml
Isolated analysis: four AI units separately read the README, analyze the API, study type definitions, and review documentation—“never seeing a single line of original source code”
Independent rebuild: behind an isolation firewall, a separate set of AIs reimplements the code from the specification
License liberation: the output code ships with the MalusCorp-0 License—zero attribution, zero copyleft, zero obligations

A leap in speed

AI’s biggest change to clean-room engineering is time compression. Malus claims:

Project	Traditional time	Malus time
IBM BIOS clone (1984)	4+ months	an entire engineering team
left-pad (11 lines of code; its 2016 deletion crashed builds worldwide)	hours of manual rewrite	10 seconds
SPACEWAR! (the first video game)	weeks	5 seconds

Developer Dan Blanchard used Anthropic’s Claude Code in early 2026 to do a similar “from scratch” MIT-licensed rewrite of the popular Python library chardet. His verdict: “What used to take a team months or even years to rewrite, AI can now do in days. This trend is irreversible.”

Business model and pricing

Malus.sh uses a usage-based pricing model:

Item	Details
Billing method	Per-KB, based on uncompressed package size
Per-package limit	10 MB
Per-run limit	50 packages
Payment methods	USD, EUR, BTC, stock options
Output license	MalusCorp-0 License
Legal protection	Claims indemnification via “an offshore subsidiary that doesn’t recognize software copyright”

The “customer testimonials” on the site are clearly satirical—e.g., “guilt doesn’t show up on quarterly reports.” But the pricing structure and payment functionality are real.

The founder’s core argument

Mike Nolan laid out Malus’s position systematically in his March 2026 blog post, “Thank You for Your Service.”

Three structural problems with open source

Cases where open source has already failed

Year	Event	Type
2016	left-pad deleted, thousands of builds crashed worldwide	Maintainer sabotage
2021	Log4Shell (CVE-2021-44228)	Critical CVE
2022	colors.js and faker.js injected with infinite loops	Maintainer protest
2022	node-ipc contained a file-deletion payload targeting Russian/Belarusian IPs	Geopolitical sabotage
2025	Shai Hulud 2.0 npm worm	Supply chain attack

On Log4Shell, Nolan wrote: “Engineers patched it over their Christmas holidays, while the people who actually maintain Log4j are mostly unpaid volunteers who received panicked emails from around the world. This isn’t the failure of any individual—it’s the natural consequence of building critical global infrastructure on code that nobody is formally responsible for maintaining.”

Enterprise compliance cost comparison

Expense item	Annual cost
SCA tools	$1.2M
OSPO team	$850K
Legal review	$700K
Incident response	$980K
CLA management	$270K
Total traditional open source compliance	$4M
Malus full liberation package	$50K/year

Nolan claims savings of 98.75%.

Response to “exploitation” accusations

Acknowledgment of the “tragedy of the commons”

Legal and ethical controversy

Arguments supporting clean-room validity

Copyright law protects expression, not ideas. The 1879 case Baker v. Selden established this principle. Phoenix Technologies successfully cloned the IBM BIOS using the clean-room method in 1984 and received court recognition. If AI-generated code differs completely from the original at the level of expression and is only functionally equivalent, then in theory it does not infringe copyright.

Core arguments questioning the authenticity of the clean room

Training data exposure: AI models have already been exposed to the original open source code during training. If the LLM’s weights contain patterns from the original code, can its output truly be considered “independent creation”?
Copyright ownership of AI output: The US Copyright Office has made clear that purely AI-generated works are not copyrightable. If Malus’s output has no human author, users can’t claim copyright protection for it either.
Inducement to infringe: marketing explicitly aimed at “circumventing copyright” may constitute inducement liability.

A highly-upvoted Slashdot comment noted: “Good luck getting a judge to agree that an AI performed a ‘clean-room’ implementation—when that very AI was trained on the code it’s ‘reinventing.’”

Another commenter added: “The Chinese Wall legal strategy requires Team A to produce the specification and Team B to produce the implementation. If these people can’t show the specification, they’re done. Arguing that a specification must exist somewhere in the abstract Platonic space of an LLM’s black-box network won’t convince a courtroom.”

Why this threatens the open source sustainability loop

The sustainability of the open source ecosystem relies on an implicit social contract:

Contributors publish code and receive reputation, collaboration opportunities, and indirect commercial value
Users comply with license obligations (attribution, copyleft, feeding improvements back)
Companies use open source to cut development costs while giving back to the ecosystem through compliance spending

The capability Malus.sh demonstrates breaks this loop on three levels:

First, the enforceability of license obligations is hollowed out. When anyone can obtain a functionally equivalent but legally independent version at near-zero cost, MIT’s attribution requirement, GPL’s copyleft constraints, and Apache’s notice-preservation clauses all lose their practical teeth.

Second, contribution incentives are eroded. If developers know their work can be copied by AI with obligations stripped away, why choose open source at all? The reward of reputation presupposes that attribution is respected—and Malus’s core selling point is precisely “zero attribution.”

Third, the motivation for corporate compliance spending disappears. Traditionally, companies invest in OSPOs, SCA tools, and legal review both as a compliance need and as an indirect way to support the open source ecosystem. When Malus cuts compliance costs from $4M to $50K, that “savings” doesn’t flow to open source projects—it simply disappears.

The “commons decay” scenario Nolan himself acknowledges in his blog describes exactly this gradual unraveling of the loop: not a sudden collapse, but a slow erosion of willingness to contribute, ultimately draining the open source commons dry.

An irreversible trend

Malus.sh itself may be an elaborately designed satire, but the capability it demonstrates is already being used seriously. Dan Blanchard’s rewrite of chardet with Claude Code shows that this technique needs no dedicated Malus platform—anyone with a mainstream AI coding tool can achieve a similar result.

Blanchard’s verdict reflects a broad consensus in the industry: “What used to take a team months or years to rewrite, AI can now do in days. I don’t think there’s any way to put the genie back in the bottle.”

The market impact of this trend is already visible. In early 2026, software stocks like Oracle were sold off over concerns that “AI can be used to rapidly replicate software functionality.”

Product Watch on TorchTree