Identifier / Programs / Linux and Unix

vagrant

Manage lightweight, reproducible, and portable development environments. Some subcommands such as box, snapshot, halt, etc. have their own usage documentation. tldr-pages

GTFOBins inherit 1 documented command

How vagrant is abused

documented by GTFOBins

inherit

Each abuse is GTFOBins's category and the options and words it uses; the full write-up is on GTFOBins's page for vagrant.

1 documented command

from GTFOBins, each read by the identifier

inherit unprivileged, with sudo

This allows to run Ruby code (...).

echo '...' >Vagrantfile
vagrant up

Identify

The command the identifier reads trips no Sigma process-creation rule. This command is, with GTFOBins’ notes, from GTFOBins, at commit acd524623f9c of 2026-05-27, under the GPL-3.0, with no warranty. Changed: Markdown is shown formatted. The source is in lolbas-gtfobins-commands.json.gz, and the full entry is on GTFOBins’s page for vagrant. The identifier reads the line that runs vagrant.

Everyday use

from tldr-pages, CC BY 4.0

Create a Vagrantfile in the current directory with the base Vagrant box

vagrant initIdentify

Create a Vagrantfile with a box from the Vagrant Public Registry

vagrant init ubuntu/focal64Identify

Start and provision the Vagrant environment

vagrant upIdentify

None of the 3 examples the identifier reads matches GTFOBins abuse or trips a Sigma process-creation rule.

vagrant

How vagrant is abused

1 documented command

Everyday use

Other programs abused for inherit