The solution to my question came from a friend that asked me to write the answer on his behalf:
Filter the repo, changing the bogus author with the following. Note that this should be on two separate lines (normally using shift+enter):
$ git filter-branch --commit-filter 'case "$GIT_AUTHOR_NAME" in > *author\<\ email*) GIT_AUTHOR_NAME=author_name; GIT_AUTHOR_EMAIL=author_email;; esac; git commit-tree "$@" '
Since the faulty commits are still in the repository,
git fsck
will still fail on them. To get rid of those commits, clone the repo and then prune unused objects:$ git clone badrepo goodrepo && cd goodrepo $ git gc --prune=all
The new repository is clean.
git fsck
returns no errors.