Shareaza

G2 specs (Q2 packet) do not define any way to identify sending client, so not possible in current implementation. Howewer, we can extend Q2 packet by adding vendor code or client name as another child packet.

Might be intelligent to do. These malformatted packets are frequent enough that it could be (and probably is) a bug of Shareaza generating them in the first place, as they do not decrease in number even though non-Shareaza clients are basically non-existent on the network - or at least there are not enough of them to produce such a big number of packets on a constant ratio...