There are so many things that could go wrong here that I don't know where to start. For your own sake, shut this functionality down.
I know you are genuinely trying to solve a problem.. But look at the comments: Three comments with the exact same reaction.
Only Hodor would get to Step 2.
Something similar to OAuth 2.0 would be better.
As things are, there's not really much that can be done unfortunately. We do plan to open source this in the near future however, which should make us seem a bit more trustworthy at least.
For now I added a note encouraging people to change their password after using the tool.
Ultimately the solution is probably for Apple to improve the process of creating certificates. Right now almost all instructions on how to do so require you to use Keychain Access (So you must be on a Mac), followed by typing commands into openssl on the command line. There's a lot of room for error and StackOverflow is filled with people running into problems during the process, so hopefully this tool saves some people time.
Initially I started working on this to be used just by our customers. After chatting with other iOS devs, we saw that messing up Push Certificates was such a common problem that we decided to make it open to everyone.