How do you deal with persistent automated attacks that keep adapting?

November 18, 2026 5 answers
Asked by 9d+florinex_263

We have automated account creation and probing against an application on AWS. The traffic has adapted to rate limits, tougher CAPTCHAs, and IP blocks, including blocks on Tor exit nodes.

What defenses are worth trying when the traffic keeps changing addresses and tactics?

Answers

7m!vornixa_582

Stop treating the IP address as the whole identity. With residential and mobile addresses in the mix, broad blocks can catch real users while the attacker just moves again.

Look at sequences instead: account creation followed by login and rapid requests to lots of pages or unusual parameter combinations. Rate limits on individual accounts and sensitive actions can complement IP limits. Start new detection rules in a monitoring mode where possible, then check for false positives before blocking.

_p61+vexlato.9:

Keep the raw request details needed to investigate, but avoid logging passwords or other sensitive values. A pattern is more useful if you can tell which accounts and actions it connects.

Reply to this answer
6p!zavluri_813

The probing matters more than whether you can stop every fake signup. Review the pages and API calls being targeted for authorization checks, especially whether one account can access another person's data. Validate inputs on the server and make sure hidden page names or client-side checks aren't the only protection.

Prioritize the actions that expose data or change something valuable. A WAF can reduce noise, but it won't fix an authorization flaw in the application.

Reply to this answer
6h+ferricup_271

Cut down the public surface where you can. Administrative tools and services that don't need to be open to everyone can sit behind private network access. Geo-blocking may help if you have a clearly limited service area, but it can also shut out legitimate users and won't stop traffic routed through allowed regions.

Reply to this answer
_t27~bravelo.5

Another bot management service might be worth evaluating, but I wouldn't assume switching providers will solve it. Compare what it can detect, how well it integrates with your current AWS setup, and what happens to legitimate users when challenges get stricter. CAPTCHA alone is clearly not stopping this campaign.

9d+florinex_263:

Moving DNS for multiple domains would be a fair bit of work, so a comparison against the current setup would help before committing to that.

Reply to this answer
RindleFox

Don't assume the changing tactics prove there's a person at the keyboard or that AI is involved. Automation can vary timing and parameters too. Group the activity by behavior and look for recurring schedules or sequences that might give you a useful detection signal.

If there's evidence of account compromise or data access, treat that separately from nuisance traffic. Preserve the relevant logs and investigate the affected accounts rather than just adding another block.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions