- Ask for the approval of the upstream developer
- Rename the package, as Debian did with Firefox/IceWeasel
The problem with the OVH images is their kernel lacks months of security patches, so they're advertising insecure images as "Ubuntu".
However, this alone isn't necessarily reason to prevent someone from distributing derived versions of your open source project using the original name.
If this was the case, Canonical would prevent people from shipping EOL'd versions of Ubuntu under any circumstances. If I ship an appliance with Ubuntu 10.04 (EOL 2013-05-09), it would have the same negative impact as shipping a patched 16.04 with no up-to-date patches or a similarly unpatchable kernel or core package.
Edit: typo
If you don't accept the Debian terms, your package ends up in "nonfree" and I honestly don't know how that is managed downstream.
I think I'm apt-get installing super-foo-blah, but during installation it's actually being patched so is deviating from what upstream are really shipping [1].
As I understand it, Canonical advocate patching upstream packages (with the noble goal of improving compatibility with their platform) and keeping the package under the same name. Just as OVH et al are doing with Ubuntu itself.
[1] http://packaging.ubuntu.com/html/patches-to-packages.html