37
History shows command I didn't run on my VPS (lemmy.ml)
submitted 1 year ago by heyfrancis@lemmy.ml to c/selfhosted@lemmy.world
11 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments
[-] heyfrancis@lemmy.ml 1 points 1 year ago

wait, the 3rd command is vi. I mean that's not an automated script, it should be executed manually, right?

[-] TheInsane42@lemmy.world 14 points 1 year ago

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.

[-] Cooljimy84@lemmy.world 3 points 1 year ago

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 ?

[-] chiisana@lemmy.chiisana.net 1 points 1 year ago

Perhaps it is listed in reverse chronological order; edit, check content, change permissions (for deployment)?

this post was submitted on 06 Aug 2023
37 points (97.4% liked)

Selfhosted

40183 readers
401 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz