Oh wow. Basically the whole infrastructure was compromised. > He began to copy one of our tables, which contained partial user information, including email IDs

Oh wow. Basically the whole infrastructure was compromised. > He began to copy one of our tables, which contained partial user information, including email IDs, hashed passwords, and last tested URL. His copy operation locked the database table, which raised alerts on our monitoring system. How does a copy operation lock a database table? Because you set thresholds on the number of reads? I find it a little surprising that such a knowledgeable hacker would make such a rookie mistake. Can someone clarify?