I'm assuming that an extension update is precisely what triggered this behavior. It sounds like the extension had no need for alert functionality, and that this

I'm assuming that an extension update is precisely what triggered this behavior. It sounds like the extension had no need for alert functionality, and that this was a first occurrence, so I'd also assume they had to add code to trigger an alert rather than just blasting a brand new alert to users via written but previously-unused code.