• Replies 14 replies
  • Subscribers 337 subscribers
  • Views 222 views
  • Users 0 members are here
Related

mass inactivation

John Trimble
$organization

I've got a manually-unmanageable number accounts created by bot activity I'd like to inactivate (not purge) while we test out improved captcha.  Can anyone point me to the code invoked by the constituent menu or possibly already have code written for this. I'm thinking there's probably more to it than updating inactive and inactive_reason in T_CUSTOMER. 

Thanks!

Parents
  • $organization

    I wanted to follow up with a few more details about our 'bot' activity in case anyone else is seeing anything like this. We are not on TNEW.  We have captcha, but it didn't catch these. We did contact Tessitura Support, and they did recommend purging, but we held off on purging to allow time for additional forensics.

    We stumbled on accounts with the following characteristics: 

    • created on website
    • all text fields except email populated with random alphabetical characters
      • range of number of alphabetical characters per field
      • zip codes also populated with random alphabetical characters
    • Googling a few of the emails showed them as flagged for spam or identified with sketchy sites
    • all drop-down values had the highest ID selected (e.g. all prefix Dr.  All country Zimbabwe)
    • About 70% have 1920-12-31 entered for a birthdate attribute.  (Might be an artifact of the entry method like the dropdowns.)
    • No transactions on any of these accounts
    • varying handfullish number created daily since November 2020 for a total over 3000 identified such accounts
Reply
  • $organization

    I wanted to follow up with a few more details about our 'bot' activity in case anyone else is seeing anything like this. We are not on TNEW.  We have captcha, but it didn't catch these. We did contact Tessitura Support, and they did recommend purging, but we held off on purging to allow time for additional forensics.

    We stumbled on accounts with the following characteristics: 

    • created on website
    • all text fields except email populated with random alphabetical characters
      • range of number of alphabetical characters per field
      • zip codes also populated with random alphabetical characters
    • Googling a few of the emails showed them as flagged for spam or identified with sketchy sites
    • all drop-down values had the highest ID selected (e.g. all prefix Dr.  All country Zimbabwe)
    • About 70% have 1920-12-31 entered for a birthdate attribute.  (Might be an artifact of the entry method like the dropdowns.)
    • No transactions on any of these accounts
    • varying handfullish number created daily since November 2020 for a total over 3000 identified such accounts
Children