It's not outside of the realm of possibility that's true, particularly if you have an earlier vintage that's still on XP, but it's more likely that they're getting traffic they aren't familiar with and it showed up in a packet
trace. Among other reasons, this is why lighting and sound consoles are usually kept isolated off of
house networks.
Before you go too far down a rabbit hole, I would ask for more specifics on how precisely they came to that conclusion. If it's just because they're seeing traffic they don't recognize, then you should rectify that to by getting the lighting systems on a dedicated
VLAN segregated from everything else. You should also make sure that there are no unmanaged Layer 2 switches in the signal path for your
console. Unmanaged Layer 2 switches take multicast packets (one packet stream getting offered up on the
network for many possible receivers to subscribe to) and turn them into broadcast (any multicast packet stream on that
switch gets regurgitated and sent out to every port and device on the
network whether they want it or not -- "a broadcast storm"). At a minimum, you want Layer 2 Managed or Layer 3 switches to avoid this.
It's much more likely that streaming lighting data is fine but is getting broadcast out to corners of the
network it isn't intended to, and not so likely that your
Ion that is a very locked down version of Embedded Windows has a virus. There is the slimmest of possibilities if you're still running XP that a security vulnerabilities are being exploited by a virus because XP hasn't received security updates for a long time but it's highly improbable that's what you're encountering.