Hello Bungie-Supportteam & Community :) I've already been in contact with the Blizzard-Support, but they redirected me here instead. This is not "directly" related to D2, so I'll make this as short but as detailed as possible. So to get straight to the point, I'm the developer of a few various "modtools" for Borderlands 2 & Borderlands The Pre Sequel. One of them is a DLL, which either of these games loads by itself (nothing is "injected" anywhere, despite its name). It can be found here: [spoiler]https://github.com/c0dycode/BL-CommandInjector[/spoiler] This also shouldn't be causing a ban in D2, since it's only loaded when either of these games is running, which was not the case from the reports we've heard about. (also "lives" in a completely different address space). This creates a NamedPipe to act as some kind of "API" between the game (Borderlands 2 or Borderlands The Pre Sequel) and 3rd party tools to send data to/receive data from the game via. the games own Console Commands. One tool that utilizes this DLL is the "Borderlands Commander", which can be found here: [spoiler]https://github.com/mopioid/Borderlands-Commander[/spoiler] This registers a few Hotkeys and upon pressing one of them, it sends the assigned Console Command via. the NamedPipe directly into Borderlands 2 for example. Now the reason why I'm posting this is: The developer of the "Borderlands Commander" & others have received a few messages of people saying that they were banned from Destiny 2 and they suspect it was due to "Borderlands Commander" still running in the background. Now, I don't expect any detailed information. I was just hoping to be able resolve this on both ends. We obviously want to avoid anybody getting banned from any unrelated games. If needed, I can also provide at least 3 Battle.Net Accountnames that are affected by this, or maybe they'll show up in here themselves. If you need any sourcecode to check for yourselves, we can provide them to hopefully resolve this for those users. Thank you so much for your time :)