We have had a particular email address used for registering a number of different participants for workshops in CIVIEVENT - and subsequently cancelling - that we believe is an immigration scam. Wondering if there is a way to disable this particular address from registering.


  • I wonder if you could create an appropriate rule using CiviRules (I thought this was better as a comment rather than an answer, since it is so light on detail). Nov 17, 2016 at 20:40
  • Thanks for this - I'll give the rules a try. For the moment we've also blacklisted the sender's email address in our hosting setup. It won't eliminate the registration problem, but it might give them a hint. Dec 4, 2016 at 16:10

2 Answers 2


Did you check your log files to see if the fraudulent Event registrations originate from the same IP (or similar)?

If so then block that IP (or entire subnet) so that it can no longer access your server.

For those using iATS Payments there is another handy anti-fraud measure: you can block credit cards originating from certain BIN countries to go through;


It's hard to answer this question without more information, but I'll give it a shot.

My first approach would be to write a CiviCRM extension using hook_civicrm_validateForm. This would give a result similar to if someone left out a required field - it would reload the page with an error.

If your goal is instead to allow them to register (and it's a free event) but not see the results, Michael M's suggestion of a CiviRule to delete the event after it's created may work.

If your goal is something else - e.g. to fake a successful event - you'd have to give more details, but is likely to be more difficult.

  • Thanks for your response. I don't have much more info to provide, unfortunately. This is a specific gmail address used to register participants for an event. Close to the event they cancel and request a refund, as "their immigration application didn't succeed." It's happened enough that we're aware it's a scam. Because the payment goes through immediately via Paypal, it seems legit and CIVICRM processes it. What we want to do is block it. The party involved could start using another email address (participant names are always unique) so I guess any approach might be a short term solution. Dec 4, 2016 at 16:15
  • @ChrisHutcheson How annoying! The validateForm hook is a good choice then, because it prevents the form from being submitted. You could also use the postProcess hook to fake a successful event registration, but kill it before it reached PayPal. They'll know they didn't succeed when the card isn't charged though. Dec 5, 2016 at 17:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.