back

by brandonb·13y ago·view on hn ↗
Hey Devon -- thanks for the thoughtful comments!

Most of our customers do use Sift Science for financial fraud, but because it's a machine learning system, you can train it to detect other types of bad behavior like spam. We have customers in production using us to detect spam, fake inventory, and duplicate accounts. If you have a use-case that doesn't quite seem to fit, let me know and we can figure out how to train our system to recognize that type of behavior: brandon@siftscience.com.

If a fraudster bypasses the JS, we still have REST events such as transactions (or any other custom event sent from the backend). Seeing a user who has REST events but no Javascript events is a suspicious signal in itself, so fraudsters can't circumvent the system by just turning off JS.

FWIW, we're on some pretty major sites that we can't announce, so we've gone through a bunch of compliance, audit, security, and other concerns already.

1 comments
Can you explain better what exactly you do?

It seems that you use ML to pinpoint fraud (or better, undesired behaviour) in $WEBSITE.

So that could be fraud detection because they login from one country, ship to another and buy a certain combination of items.

Or that could be "spam fighting" because they create an account with X and Y characteristics and post similar things.

Am I right in my perception? (and you could use this not only for 'bad behaviour' but for good behaviour as well)

You're right on. In theory, you could train our system to recognize good behavior if you sent us enough $label events, but most of the patterns we have today are really optimized around detecting bad behavior.
Could you develop a little more how duplicate accounts could be detected?