Hi @strathq,
email well received and responded already. I’ll post my response to you below to give context to your post.
Hi Gary,
Thanks for sending the scan report, and sorry for the worry. This is a false alarm, and your site is safe to keep using.
Why the scanner flagged it
The rule your host’s scanner matched is called php.file.put.contents.temp.name.curl.exec.unlink. The name lists the four PHP functions it looks for. The scanner doesn’t check what the code does with them. It flags any file that uses all four, because malware often does: it downloads a file, saves it, runs it and deletes the traces.
smallpotato-api.php runs your CMS admin. It uses each of the four for a normal admin task:
-curl_exec downloads from another website. Your admin uses it for the AI writing assistant, for YouTube and Vimeo video links, and for importing photos or a Google Sheet from a web address.
-tempnam / tmp_name handle temporary files. tmp_name is where PHP puts any file you upload (images, PDFs, MP3s, backups). tempnam makes a short-lived temporary file while a downloaded photo or an imported sheet is checked and saved.
-file_put_contents saves data. Your pages, posts, collections, settings and backups are stored in files, so every save in the admin uses it.
-unlink deletes a file. It runs when you delete an image, post or collection item, when old revisions and backups are cleared, and when a temporary file is cleaned up.
All of these run only from your admin.
What I’d suggest now:
-
Upload the file again from your own export. In the folder Blocs exported for your site, find includes/smallpotato-api.php and upload it over the copy on your server. This replaces the server copy with the one Blocs made, so you know it hasn’t been changed.
-
Tell your host it’s a false positive. You can quote the rule name and the explanation above. Most hosts let you mark the file as safe, or their support can whitelist it. If the file has been quarantined, restore it or upload it again, or your admin page will stop working.
I will add a permanent fix for this in the upcoming version 
In the next update (SmallPotato CMS 2.1), the code that uses curl_exec i will move into its own file. That file never writes or deletes anything. After the update, no SmallPotato file has all four functions, so this rule won’t match. When you install 2.1, click the SmallPotato Admin Bric once in Blocs before you export, so Blocs includes the new file.
If your host asks for more detail, send me what they say and I’ll help.
Kind regards,