I believe this error is caused by the decryption of your ViewState using an obsolete ViewStateUserKey.
Removing these errors is a two-step process:
- Make sure you have a site verification key. You can use several online resources to generate one of them, for example this one .
- Make sure the ViewStateUserKey page is always consistent. From the MSDN documentation:
Setting the ViewStateUserKey property can help you prevent attacks on your application from malicious users. It does this by letting you assign the identifier of the view state variable to individual users so that they cannot use the variable to generate an attack. You can set this property for any string value, such as a user session identifier or an authenticated user name.
You can do this by setting it yourself (possibly in your Page or basic Page Init event):
if (Session["ViewStateUserKey"] == null) { Session["ViewStateUserKey"] = new Guid().ToString(); } this.Page.ViewStateUserKey = Session["ViewStateUserKey"].ToString();
And no, I donβt think you were hacked.
Paul suart
source share