That's a common error triggered by SSH scanning bots and the like when you've configured sshd to only use modern ciphers, because they tend to use really ancient versions of libssh, or whatever SSH client is available on the compromised system they're running from. You can safely ignore those messages.