If you have trouble finding this I would recommend drafting your own, basically starting from the qualifications you need and saying those qualifications supercede the included open source license you prefer (MIT, Creative Commons etc).
I've been involved with the software industry for a very long time (since late 70s). I have also had significant exposure to the dark underbelly of the legal system where legal research is no stranger to me. I have patented software, so that too is familiar ground.
Yet, things change all the time so your question does require current research to arrive at a reasonable conclusion to your question. How deep into this rabbit hole you want to go is a fair question to ask.
With a quick google search and reading of this: http://opensource.org/faq
, I don't believe placing restrictions on binaries will fall under any of the standard open source licenses commonly used. Anything non-standard would have to be evaluated, which again gets back to how deep into the legal rabbit hole you want to go.
IMO, informed by much life experience in such matters, writing your own document in plain English to establish your clear intent is at least the starting point. Having that text reviewed by an attorney or paralegal is another level of due-diligence you may wish to take, but then again relying on the legal system to decide if a violation has occurred and what options you have to claim damages and pursue recovery is a crap shoot at best.
Your best course of action is to write your intention and perhaps the reasons for the restrictions in your own words in your own custom license text.