I don't see anything related to architecture other than 32-bit and 64-bit. As they don't specify, the packages are most likely compiled for x86 architectures. The Apollo CPU is ARM based. The error messages would tell you specifically.

It doesn't appear to be open source. You could contact support, and see if they would supply an ARM version.

Another option would be to run the monitor on a different platform, and remotely shut down attached ARM based systems from there.

Assuming you have a consumer-grade router with DMZ enabled, your Apollo was likely compromised in seconds than minutes!
Never ever put any device in such a DMZ without knowing what you are doing. (Such consumer-grade DMZs have most likely every port open - from SSH, HTTP, HTTPS, every port from 0 to 65535 ...)

So, it seems your brother figured it out! Good! Remove Apollo from DMZ and back in the LAN where it should belong firsthand.

Reset the Apollo to factory defaults and start hashing without any more disturbance.

First of all, why are you doing that? It's not required to forward that port to run a full node.

Of course, if someone planted a script on your machine that periodically goes to the config file and changes the pool settings, changing password doesn't help, because they're already inside.

I am myself considering installing my own Linux distro on mine & connecting the Apollo 'to itself' using a short USB-A => Micro-USB cable, in light of these vulnerability reports. Had no issues with it so far, though.

Let's stop with the fear mongering please. Only you and one other person has reported this, and support has been in touch with one of you. Its been determined the issue is because you guys chose to expose your Apollo to the whole internet for anyone to attack. This akin to leaving your Bitcoin wallet on a table outside, publicly yelling out your address and telling everyone come and take it.

The issue is with forwarding our webUI to the open internet. The webui is not a server grade hardened frontend, its designed for easy access and control of your Apollo from your LAN. While you can forward your WAN port 80 so you can bring your UI up from any and device/place what you are doing is essentially hosting it as a public web page that anyone can try to attack, and this is precisely what happened.

Simply remove those port forwards and you will be fine(or go through the process of turning your Apollo into a hardened server grade web server). If you really want to be able to access your Apollo from outside your LAN in an easy and more secure way, then setup a remote access app directly in the desktop environment.

yep i've used multiple.  i am not currently using slushpool however.  its so strange, i go through all these steps.  it runs fine on the pool i set, then at random it will go back to this topminero1 workername on slushpool as others have seen.  with reflashing and all that and setting the default pool to something totally different, i just can't understand how it keeps changing without some sort of a compromise or something.  like i said, after yesterday, it had a new network, new ip, isoloated from anything else in my network, all the passwords on the unit that i know of changed, unless there's more i don't know about or some kind of a virus or bug or something....

Actually to be fair I'm not sure they work alerting for block finding since ckpool went solo.

But the apps I know of that work with ckpool are:

Apple: Ckpool Stats - https://apps.apple.com/gb/app/ckpool-stats/id1076177533
Android: CheckPool - https://play.google.com/store/apps/details?id=com.alexdib.miningpoolmonitor

I've never found a solo block here so tbh I don't know if they do what you want. But some others have come up with good solutions based on wallet alerts.

If you want to do wallet alerts, you can also use Sentinel on Android https://play.google.com/store/apps/details?id=com.samourai.sentinel

let me know if this is working for you  and if so give a description of how you went about it please.  thanks!

I feel the same way, I've reflashed, made sure the SSD is seated well, used a USB cable to see if the hashboard was bad absolutely nothing wrong with it, temps are in a great range - I even went as far as putting it in ECO mode... after about an hour I get the notification that my miner was disconnected, log back into the dashboard to see the pool settings are once again changed..

What's odd, is it's completely random times when this happens, the first 7 days were flawless mining and then randomly on the 8th day it started changing the pool settings - again sometimes it'll be hours, then sometimes I have to sit there and change the pool settings 5 times within an hour - reboot - let the node start - start miner (sometimes have to click start 5-10 times before it'll become active to where the dashboard pops up) start hashing and then be fine and connected to my pool for 10+ hours..

Makes absolutely no sense other than a back door or something.

There are apps that will alert you on your phone if that helps

It seems like someone figured out a way to exploit the FutureBit, there's nothing I can pinpoint in any of the files available on the FutureBit that were edited for the miner to keep switching to some person's miner.

I have had external fans on my setup for months, temps have been in the 40's.  this issue with the pool automatically changing just started within the last week.  I have relflashed and changed passwords.  it ran for a few hours and then automatically changed to that same slushpool address and topminer01.  I don't think this is a temp issue........  not really sure what is going on.  i just shut mine down until there is a resolutions.  i'm not letting my unit run while someone else is getting the perks from it.....

You can just run a cron job that runs every minute or so that fetches the latest stats from ckpool and the current difficulty from an explorer like mempool.space and then compare your best share with the current difficulty.

If your best share is larger than current difficulty, then you probably hit a block, so send an email.