Support

When Akeeba Backup is running it needs to keep a temporary "memory" of its backup engine's state between individual page loads or remote API calls which step through the backup process. It does that by serialising its internal objects, encode them with base64 and put them in a .php file with a single die statement at the top of the file. This is done for security reasons. If someone were to try and access that file – which contains privileged information – directly from the web they'd get a blank page with no content.

This file is removed at the end of a successful backup. If the backup is stuck for more than three minutes or belongs to a failed backup that ran at least 3 minutes ago it will also be removed the next time you visit Akeeba Backup's control panel or start a new backup.

The file in question seems to be one of those "memory" files, left behind when a remote backup through the JSON API failed to run to completion. If you visit the Akeeba Backup control panel page it should go away.

If the file doesn't go away, check its contents. If the top line is a die statement it's OK, you can delete it manually. If it's something else there's a remote possibility that it is a malicious file, put there by an attacker who's trying to disguise their actions.