← All investigations
Investigation 033Digital rights management

Why Did Sony BMG Put Hidden Software on Music CDs That Made Computers Less Secure?

Sony BMG tried to curb casual copying with two CD software systems, but XCP concealed itself broadly enough to hide malicious code while MediaMax introduced separate consent and security failures.

Why Did Sony BMG Put Hidden Software on Music CDs That Made Computers Less Secure? investigation cover
Upcoming investigationPremiere scheduled

Premieres November 5, 2026 at 8:00 PM CST. The video will play here after its scheduled YouTube release.

Read the evidence, decisions, and consequences behind this investigation.

The question: The Disc That Hid Itself

Why Did Sony BMG Put Hidden Software on Music CDs That Made Computers Less Secure?

In two thousand five, Sony BMG sold ordinary music CDs carrying copy protection for Windows computers. One system, called X C P, did more than limit copying: it concealed parts of itself deep inside the computer. Its hiding method was so broad that malicious software could use the same hiding place.

So the reversal was almost perfect. Software meant to protect Sony BMG's music could help conceal threats on the computers of the people who had paid for that music.

And the public learned about it because one security expert found something on his own P C that was not supposed to be visible.

A Real Problem, an Aggressive Answer

The record business did have a problem. By two thousand five, label executives saw peer-to-peer sharing, inexpensive C D burners, and easy digital copying as threats to their control over how music moved.

Sony BMG executive Thomas Hesse publicly described casual or school-yard copying as a major target: not a professional counterfeiting ring, but one buyer passing copies to friends, who could then make more copies.

Sony BMG's answer was to make a music disc behave differently inside a computer. It licensed X C P from a British company called First Four Internet and MediaMax from SunnComm. These were two separate systems, and that distinction matters because they installed differently, failed differently, and were not covered by exactly the same remedies.

Both were attempts to restore control to the label after the customer had bought the disc. They were intended to play like albums in conventional C D players. On a Windows P C, they could create a controlled listening and copying environment.

That split was the key to the whole strategy. The music still arrived on a familiar silver disc, but inserting that disc into a Windows P C could launch label-approved software with its own rules. The customer saw an album; Sony BMG saw a point where control might be rebuilt.

But control on somebody else's computer creates a different responsibility. If the software installs quietly, buries its components, or cannot be safely removed, the record label is no longer just protecting a song. It is changing a machine it does not own.

That tradeoff might have remained obscure if not for a tool built to expose hidden software.

The Files That Shouldn't Be There

In late October two thousand five, Mark Russinovich, a Windows expert and co-founder of Sysinternals, was testing a program called RootkitRevealer on one of his own computers. The scan reported files and registry entries that ordinary Windows tools could not see.

Russinovich traced them back to a C D he had played: Van Zant's Get Right With the Man. On October thirty-first, he published his findings under a title that made the accusation unmistakable: Sony, Rootkits and Digital Rights Management Gone Too Far.

X C P had installed a driver that hid files, processes, and registry entries whose names began with a particular prefix. That concealment was not limited to Sony BMG's own files. Anything using the same naming pattern could disappear from normal view—including malicious code.

Rootkit-style concealment is dangerous because it can make the computer's normal view of itself unreliable. A file can still exist and still run while the tools a user trusts fail to show it. X C P brought that kind of concealment into a consumer product, not because Sony BMG set out to help attackers, but because hiding the copy-protection software made it harder for users to disable.

And removal was not straightforward. X C P did not appear in the ordinary Add or Remove Programs list, and the disc did not provide a normal uninstaller.

Russinovich had turned a private design choice into a public security story. The issue was no longer merely how many copies a buyer could burn. It was whether a record label's software could enter a customer's computer, conceal itself, and leave behind a capability that attackers could borrow.

Two Systems, Two Sets of Risks

The scandal is often compressed into one word: rootkit. But that shortcut blurs the evidence.

X C P was the system with the rootkit-like cloaking mechanism. MediaMax did not behave the same way. Researchers found that MediaMax files could be placed on a Windows computer before a user accepted the license agreement and could remain after the user declined it. MediaMax version five point zero also created a separate privilege-escalation vulnerability.

In plain English, that flaw could let software operating with limited permission gain more power than it should have. That was not X C P's hiding trick, which is why collapsing both products into one Sony rootkit story misses how broad the failure really was. Different vendors had delivered different systems, but both reduced the computer owner's informed control.

The systems also restricted ordinary uses, including direct disc copies and transfers to some portable music players. Their bundled players could send an I P address and an album-identifying key to retrieve targeted images or promotional messages.

Yet the protection itself was weak. Researchers documented simple workarounds, meaning a determined copier could evade controls while an ordinary customer absorbed the installation and security risk.

The scale made those design choices impossible to dismiss as a tiny experiment. The Federal Trade Commission later alleged that Sony BMG put content-protection software on more than one hundred C D titles and sold about three million X C P discs, eight point four million MediaMax version three point zero discs, and five point seven million MediaMax version five point zero discs.

Those are discs sold, not a count of installed software, infected computers, damaged machines, or successful attacks. The number of machines actually compromised by attackers was not established by those sales figures. But every additional disc widened the population exposed to a decision customers were poorly equipped to evaluate.

The Fix Becomes Another Problem

Sony BMG first offered a decloaking update rather than a complete X C P removal tool. That changed what users could see, but it did not cleanly unwind the original installation.

Then the recovery effort produced another reversal. Researchers found vulnerabilities in the original web-based X C P and MediaMax uninstallers. A malicious website could use those flaws to run code on a visitor's computer.

Meanwhile, at least two Trojan horses seen in the wild used X C P's cloaking behavior to hide malicious files. The possibility Russinovich had described was no longer merely theoretical, although the evidence does not establish widespread successful compromise.

That development changed the stakes again. A debate that might have sounded like an argument over license agreements now involved code written by outsiders taking advantage of a hiding mechanism already sitting on customers' machines. Sony BMG did not write that malware, but X C P's design had supplied the cover.

As technical warnings spread and public pressure grew, the original business logic looked less defensible. Sony BMG wanted to make casual copying harder. Instead, its protection was bypassable, its presence was difficult to understand or remove, and its repairs created additional danger.

The obstacle was no longer piracy. It was the protection system itself.

Recall and State Relief

Under mounting technical and public pressure, Sony BMG suspended production of X C P discs, asked retailers to remove affected X C P titles, recalled those discs, and offered exchanges. The recall applied to affected X C P discs; it should not be casually expanded to every MediaMax title.

Legal consequences followed on several tracks. A consumer class-action settlement created exchange and compensation options. California separately alleged that Sony BMG had manufactured more than twelve point six million C Ds containing the two systems between January and November two thousand five. Its settlement included penalties and costs, restrictions on future conduct, and reimbursement of as much as one hundred seventy-five dollars for documented qualifying repair expenses in California.

Federal Rules

Then, in two thousand seven, the Federal Trade Commission settled its own charges. Sony BMG agreed to clearer packaging disclosures, affirmative permission before installation, reasonable uninstall tools, exchanges, limits on using previously collected information for marketing, and reimbursement of up to one hundred fifty dollars for qualifying repair costs caused by attempts to uninstall X C P before the current uninstaller was available.

Those remedies trace the alleged failure almost point by point. Notice answered concealment. Permission answered installation without informed choice. A reasonable uninstaller answered software that customers could not safely remove. And repair reimbursement recognized that control imposed on the customer's computer could create costs beyond the price of the album.

The F T C settlement was not an admission that Sony BMG had violated the law or that the complaint's non-jurisdictional allegations were true. And the agency did not ban digital rights management. It targeted the way the software had allegedly been installed, concealed, monitored, secured, and removed.

That distinction matters. The lesson was not that a company could never protect copyrighted work. It was that protection could not silently transfer the risk to the customer's property.

The answer: Who Paid for the Protection?

So, why did Sony BMG put hidden software on music C Ds that made computers less secure?

Because it saw casual copying as a threat and licensed aggressive tools to regain control after the sale. But in that calculation, informed consent, privacy, safe removal, and computer security became costs carried by the customer.

The software could frustrate ordinary uses without stopping determined copying. X C P could hide more than itself. The attempted fixes opened still more holes. And the result was an X C P recall, consumer relief, state penalties, and federal rules that forced the label to give customers more notice and control.

Sony BMG tried to protect its music by taking control of the buyer's computer. The scandal showed why that equation fails: a company cannot defend its property by secretly weakening yours.

Sources & further reading

Follow the record.

Join the discussion

What did this story make you question?

Comments are reviewed before they appear publicly. Your email is optional and never published.