This line shows running command as grep --color=auto jsextension, which is the process reading output from ps -aux - the command you ran. When then command has executed, the PID no longer exists, hence you aren’t able to kill it
✗ kill -9 12733
kill: sending signal to 12733 failed: No such process
I had 3 terminals (alacritty) running, and fourth one is the grep command reading output from ps -aux.
Best confirmation will be to comment at the GitHub issue link you posted and ask others what they observed if their system was infected. I’m no security expert. All I can confirm is that there is no process by jsextension that is running. But is it confirmed that its not running by a different name?
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
If I were you, I’d stop using that particular machine temporarily until I were confirmed that I’m safe from malware. If I had to use the machine anyways, I’d wipe and reinstall.
You are just trying to kill that grep jsextension you just called but it was already closed when it printed you the result.
You can also try
killall -r
That will close every instance of the process based on its name and not directly PID. -r (regex) can help you if you do not know exactly the name of the process so you can use something like ^.*jsextension.*$ which will match any process name which contains string jsextension.
Or investigate all your processes in pstree and look for parent process that spawns jsextension and kill that (it may have completely different name).
edit:
By the way
This may be interesting for you @flyingcakes since you used ps -aux and not ps aux. From ps man page.
Note that ps -aux is distinct from ps aux. The POSIX and UNIX standards require that ps -aux print all processes owned by a user named x, as well as printing all processes that would be selected by the -a option. If the user named x does not exist, this ps may interpret the command as ps aux instead and print a warning. This behavior is intended to aid in transitioning old scripts and habits. It is fragile, subject to change, and thus should not be relied upon.