The MSR606: What a $30 Magstripe Reader/Writer Actually Does

2026-08-26

The MSR606 is a small USB device, widely sold on general electronics marketplaces for well under $50, that reads and writes the magnetic stripe on the back of a card. It shows up constantly in two very different contexts: hobbyists and access-control installers using it for exactly what it's built for, and card fraud, where it's the last step that turns stolen card data into a physical, swipeable card. The device itself is completely agnostic to which of those it's doing -- it just moves bytes onto a stripe. The legality and harm live entirely in what data goes in and whose card it ends up on.

What's actually on a magnetic stripe

A card's stripe holds up to three parallel tracks of data, a format standardized decades ago (ISO/IEC 7811) and still what nearly every swipe-capable reader in the world expects:

None of this is encrypted or signed. A magstripe is a passive analog recording -- whatever pattern of magnetic flux transitions is on the tape gets read back as a fixed string of digits, with no cryptographic check that the string came from a real, un-tampered card. This is the entire reason chip cards (EMV) exist: a chip can run a cryptographic challenge-response per transaction, while a stripe just plays back the same static data every time, forever. Anything that can read that static string can write it onto another card.

What the device does, mechanically

The MSR606 (and its more common sibling, the MSR605X) connects over USB and ships with Windows software that talks to it over a simple serial protocol. In practice, using it involves three separate operations:

The coercivity setting (Hi-Co vs. Lo-Co) has to match the blank card's stripe material or the write will fail to hold -- Hi-Co stripes (the black ones, used on most bank cards) need a stronger field than Lo-Co (the brown ones, common on hotel keys and gift cards). This is the most common reason a first attempt at using one of these devices doesn't work: wrong coercivity setting for the card stock in hand.

Where this is legitimate

The common thread: the data being written either belongs to the person doing the writing, or was generated specifically as test data that was never live in the first place.

Where this becomes fraud

The device doesn't change at all -- what changes is the source of the Track 2 data being fed into the "write" step. Two supply chains feed that step almost universally:

Once a buyer has Track 2 data from either source, an encoder and a box of blank Hi-Co cards is the entire remaining toolchain to produce a working physical clone -- no different mechanically from the legitimate hotel-key use case above, just with someone else's account number in the write buffer.

Where it breaks