Payload profiles provide a variety of options to configure and build payloads. These payload configurations work independent of the Listener Profiles. This means you can edit, delete or create new profiles and use them dynamically during process injections, profile migration or to create new executable/shellcode/dll/ps1 or service executables out of them. There are 4 types of payload profiles.
The pcinject command takes a badger’s payload profile as an argument and injects it into a given process ID. The pc in pcinject stands for payload configuration. The below figure shows an example of profile injection for DnsOverHttps and SMB Profile. You can inject any type of profile using the pcinject command.