Currently if I "aws-vault foobar" and don't have a foobar profile in my aws config file, a profile section will be added and written to the file. However, if I then /remove/ the credentials, the profile section remains despite being empty. The expected behavior from me would be that if the profile were still empty (that is, never filled with extra data by the user), then it would be removed.

It'd be good to throw some error codes, as well as the message. Identifying the wrong decryption key right now is quite difficult because you need to compare the whole string.

Empire has a persistence implant called Install-SSP (See #9) which already supports dropping password filter implants on compromised machines. Instead of creating a new persistence module we should leverage the existing module and embed the exfitration parameters inside the DLL.

This will require a custom build of the implant but should integrate more nicely.

We could optionally make a sma