My guess is that ES3YJ put out such a big signal that ES2RR’s receiver got overloaded and decoded the signal at various unwanted mixer product frequencies.
If this particular case happens frequently, you could consider adding a “not Spotter callsign” condition for ES2RR.