Sock Puppet Accounts/Phase4 Long Term Storage
Principle
Putting a sock into storage is unreliable at best. Not using an account for extended periods is not “normal” human behavior. Anticipate multiple security checks, so the basic principle is to stack up verification methods and take good notes. Good luck!
Return to Puppet Creation Outline.
Actions
Best Practice: The best practice is maintaining the sock with regular activity, but this requires more time and effort than one may assume.
Take excellent notes: Log as much as possible about the last time the sock account was used, directly in KeePass or another note-taking method. Consider logging:
Date-time
IP address/region
User-agent string
Case/topic used for
Ensure all accounts have a recovery e-mail address and non-SMS 2FA:
Download “verification codes” or one-time log-in codes.
Backup 2FA secrets.
Remove the original phone number as a recovery option if possible.
Consider porting your temporary phone number to Google Voice or another VoIP service (~$20):
- Your accounts are already established, so you should be able to use a VoIP service to continue using the number.
- This may not work well for high-value accounts (e.g., Facebook), as they often require uploading a government ID before allowing a ported number to be used long-term.
Automation: Automating social media posts with a bot is an option, but it can make the account look suspicious to the platforms.