What is the problem? 

For some unknown reason the preview icon on OCP OperatorHub doesn't work properly - We are seeing different colors for different versions of our operators (Upstream is Blue icon, and Downstream is Red icon), even though we specify the content for those icons in the metadata rather than any particular filename.
After installation we see the "right" colors under "Installed Operators".

What is the difference between the versions?

• Upstream we use our icon with Blue background, and the support is Medik8s (we can see it also in the photos you have attached in the previous email, e.g. provided by medik8s Vs. provided by Red Hat), e.g. NMO https://github.com/medik8s/node-maintenance-operator/blob/main/bundle/manifests/node-maintenance-operator.clusterserviceversion.yaml#L28.
• Downstream we use the same icon as in upstream but with Red background, and the support is Red Hat e.g. http://pkgs.devel.redhat.com/cgit/containers/node-maintenance-operator-bundle/tree/bundle/manifests/node-maintenance-operator.clusterserviceversion.yaml?h=rhwa-nmo-4.11-rhel-8#n30.

The bug might be present since the upstream and downstream versions have the same API/CRD and package name IIRC. Maybe the icon is fetched by the package name and it is cached by the browser. 

Examples:

In the picture below we see both of the versions, upstream and downstream, with a Blue preview icon after installing the downstream version (NMO v4.10.0)

But the opposite can happen. Seeing both of the versions, upstream and downstream, with a Red preview icon after installing the downstream version (NMO v4.10.0).

Moreover, sometimes their colors are also flipped (community being red, Red Hat being blue).

We have been trying to use different browser (clean cache and cookies for this one), and somehow the page is downloading incorrect icon for the operators.

Today (August 1st 2022)

Today we have released downstream our three operators downstream(https://errata.devel.redhat.com/advisory/97702, https://errata.devel.redhat.com/advisory/97701, and https://errata.devel.redhat.com/advisory/97352), and we have noticed that this problem is relevant also for NMO v4.11 in OCP 4.11, and even to NHC v0.3.0 in OCP 4.11.
See below in the comments.