I think it is better to take a hybrid approach to this. Make newly created accounts can only contribute to #Hacktoberfest repos, and older account can still contribute to any repository while still being counted.
I'm not sure about that. Almost every developer I know has a GitHub account so I assume most people including spammers finding out about Hacktoberfest would already have an account that qualifies.
To draw out a hypothesis: existing accounts with real names and projects may value their reputation enough to not spam. Perhaps a reasonable line of thinking is spam accounts are newly created “anonymous” accounts.
I haven’t looked, so I don’t know if there is any correlation. It’s an imperfect filter for spammers since of course anonymous accounts already exist.
"Real" names are even easier to write than spam PRs.
Sincerely,
John Smith
So what do you do to fend off the accounts created this year to get around this rule next year?