feat: add abuse protection with throttler + logging to Postgres#386
Merged
Conversation
BigBen-7
approved these changes
Oct 2, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds abuse protection to critical APIs using @nestjs/throttler and logs blocked attempts into Postgres for auditing.
Related Issues
Closes issue #351
Changes Made
How to Test
npm run start:dev.abuse_logstable with endpoint, ip, reason.Next Steps
@Throttle()decorators to futureauth,purchase, andtransfermodules once they are created.Screenshots (if applicable)
Checklist
Additional note for future Contributors
abuse_logstable for monitoring suspicious activity.