Hey guys, I saw this in my VPS when checking history:
1 chmod +x /usr/lib/virt-sysprep/scripts/0001-swapoff--dev-vda2-mkswap--dev-vda2-swapon--dev-vda2-resize2f
2 cat /usr/lib/virt-sysprep/scripts/0001-swapoff--dev-vda2-mkswap--dev-vda2-swapon--dev-vda2-resize2f
3 vi /usr/lib/virt-sysprep/scripts/0001-swapoff--dev-vda2-mkswap--dev-vda2-swapon--dev-vda2-resize2f
here is the content of the script:
# cat /usr/lib/virt-sysprep/scripts/0001-swapoff--dev-vda2-mkswap--dev-vda2-swapon--dev-vda2-resize2f
swapoff /dev/vda2;mkswap /dev/vda2;swapon /dev/vda2;resize2fs /dev/vda1;yum -y update;systemctl disable guestfs-firstboot;reboot
This is a new server I provisioned on my VPS in racknerd. The command looks safe, but I’m wondering if these commands were executed on its own? Or someone has logged in to my VPS? This is also not normal, isn’t it?
EDIT:
confirmed, commands are still in history after reinstalling OS. As others have said, maybe the image builder ran commands and forgot to clear history
From the location of that script usr lib virt-sysprep looks to be a script put in the image by the provided to do a few things on first boot. Would have thought it was normal, but you can always ask them to double check
I confirm that VPS companies use custom images with additional scripts. I’ve seen those a few times.
wait, the 3rd command is
vi. I mean that’s not an automated script, it should be executed manually, right?I’d say they made the image, started it, did minor adjustments and didn’t delete the command history before stopping it and starting to deploy the image.
Looks harmless, although a tad sloppy.
Good point, what happens if you run that command ? It might also just left over from when they made the custom image and forgot to clean it all up ?
deleted by creator
Perhaps it is listed in reverse chronological order; edit, check content, change permissions (for deployment)?
good point, it’s just a test server for now so I’ll try to reinstall OS and check if same commands will show in history
confirmed, commands are still in history after reinstalling OS. As others have said, maybe the image builder ran commands and forgot to clear history
i contacted support and they provided me this doc page
https://support.solusvm.com/hc/en-us/articles/360007449180-How-to-modify-first-boot-script-in-the-TDN-KVM-template-in-SolusVM-