No matter whether you use the custom builds it regularly releases, you must have surely heard of the CyanogenMod team and the work it does for the Android community.

While we usually cover the latest CM versions in our CyanogenMod-related posts, we’re going to take a different turn today and talk about despicable acts and the human greedy nature.

We heard that one member of the team that goes by the name of SatanR1 – great nickname in light of the events we’re going to talk about –  or the person that registered the domain back a long time ago when the team was not as popular as it is today and then donated it, decided to impersonate Steve Kondik aka Cyanogen and ask for money from various companies in the name of CyanogenMod, funds that were apparently used in his own interest.

When confronted about the matter and asked to hand over access to, he refused to do it unless the team paid him 10,000 USD.

Obviously, the team refused, and moved operations to, while also changing ownership of the social accounts that SatanR1 had also access to. When realizing what happened, he further threatened the team, deciding to take down for good:

“Hi, so you think by removing all my access across the infrastructure was going to be a great idea? We had a chat yesterday, you’ve decided to end this bitter. How about I just change the DNS entries right now. CM will practically go down.”

The same person also managed the team’s Google Apps for Business account, so all the CyanogenMod email address you may have been familiar with, were “to be considered discontinued until further notice,” according to a blog post dated November 14.

Naturally, the team took further action, initiating a dispute with ICANN to get back its domain, and encouraging companies that may have entered an agreement with this rogue team member to send in details about how “widespread this was before [they] file charges.”

All these events were posted by the CyanogenMod Team on Wednesday in a lengthy post on its blog, but it looks like things have been resolved by Thursday. The team will get to control although, hence forward, you’ll have to get used with instead, which will be the primary domain for getting custom CM builds.

The team also mentioned that it’s taking steps for such events not to occur in the future, and we’re certainly happy to hear that in the end things were resolved.