We have detected some sort of remote packet that triggered an assert (which stops komodod).

It could just be some sporadic thing, but it is possible it is a deliberate action. The effect is that your node might be stopped and you have to start it again. Annoying, but since it might be part of a two part attack, we took the precaution to alert bittrex.

We are working on a fix and this doesnt affect trading, just deposits and withdraws.

So, if you are hit with this, then just restart komodo. I estimate about 10% of nodes are affected. And 90% of those are able to just resume. If restarting komodo doesnt work, try loading it in gdb with a breakpoint at main, and then continue. This works around the assert. If that doesnt work, then you will have to wait for an update.

A proposed fix is in the beta branch now, but it could well require more changes as we just started testing it.