Putting this together: you simply get paid developer accounts from Apple (you will need to keep getting more of these, as you will run up against the 100 device limit), ignore the part of the contract you sign that states that you are not allowed to redistribute the certificates they give you, and instead automate a process to log in to Apple's portal, add a UDID to your account, and download an updated provisioning certificate.
Connect this up with a payment processor that is willing to look the other way and an app that is capable of doing the signature process for apps locally for the user, and you are done. The device is already capable of installing certificates and applications that are signed by them from websites (see Test Flight for a commonly-used legitimate example), so the final steps are easy.
(With an Enterprise account, you don't have to worry about the number of devices; however, the contract terms are much stricter, the system has more mechanisms for Apple to turn you off, and Apple will probably care more if you attempt to abuse it. In essence, an app signed by an Enterprise certificate can be installed on any device, anywhere, at any time until the certificate's three-year expiration date hits.)
Once you are only talking about hundreds or even in the low thousands of devices (as opposed to tens of millions), you can satisfy the demand by getting a bunch of friends from your high-school class (the developer of Zeusmos was 15) to register for individual developer accounts and then contribute their Apple ID and passwords to a pool.
Based on what it says in the article (edit: which a friend of mine is telling me might be wrong, so maybe these people are doing something more complex), the other product (Kuaiyong) was using a single Apple Enterprise certificate: you only need one of these to satisfy an infinite number of devices, and they probably were signing the stuff on their server rather than on the client (so not redistributing the certificate).
That said, the rules on how you can use an enterprise distribution certificate are quite strict: you can sign applications used only by 1) employees of your company; 2) customers of your company who are physically present at your company's place of business; or 3) customers of your company who are being physically supervised by an employee of your company while at another location.
The developer of this program keeps opening PayPal accounts, and PayPal keeps shutting them down. In just December, this developer got two PayPal accounts shut down; the latest one was only used for four days before it was whacked.
Dec 24: "PayPal is back online for http://zeusmos.com and http://uhelios.com – Happy Holidays everybody!" -- https://twitter.com/uhelios/status/283260362919395328
Dec 28: "I'm absolutely done with PayPal. This is ridiculous." -- https://twitter.com/uhelios/status/284654128339243009
However, despite careful and detailed explanations to Stripe--and despite them saying they would look into the matter--this website has been operating and taking payments using their payment processing system for months.
Also, while the developer of Zeusmos claims in the "update" to the article that his application was never supposed to encourage piracy, it came by default with its search results coming from a website called AppTrackr, a large repository of cracked applications.
In the last few months, the developer decided he wanted to "stray away from AppTrackr", but the result was not to move further from piracy: it was to become less reliant on that one piracy site and instead use another one called AppCake.
Meanwhile, the developer has often compared his service to Installous, saying on his Twitter account that "its somewhat like Installous, but better"[1] and that it "has many features that Installous does not excel at very well"[2].
[1]: https://twitter.com/uhelios/status/274859392812318720
[2]: https://twitter.com/uhelios/status/239863143793324032