A behaviour check before go-live. A compromised update can leave every page working. On the test copy, Verploy now also looks at what an update does: new administrators or extra permissions, a new must-use plugin, a plugin folder that doesn’t belong to the update, PHP files in uploads, options with known backdoor names, new scheduled tasks and connections to new servers. You see the result in the update’s timeline. For now this is a notice only; it does not hold an update back.
Connector 2.26. The behaviour check needs Connector 2.26. Verploy updates the connector by itself. The image check is also stricter, so ordinary images are no longer reported as PHP in uploads.