You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Integrate Fraud Protection from Group-IB into NewDot #68284
Our product is intentionally designed for viral adoption and frictionless onboarding, allowing users to create accounts and engage with features without immediate verification. While this design supports rapid growth and easy collaboration, it also makes the platform inherently vulnerable to abuse. Malicious actors can exploit these flows to create accounts and send unsolicited content, effectively using the product as a spam distribution channel.
Why is this important?
It affects our reputation and user trust, and pollutes our database with thousands of unvalidated accounts.
Solution
Integrate Group-IB into NewDot and send events to their fraud protection server to analyze the common behaviour of attackers who abuse our viral onboarding flows.
App PR is also ready for merge, but held on the OldApp
Next Steps
Initialize the FP code and do the setup by setting the login status, accountID, email and whatever other metadata we send when we init FP in OldDot web
changed the title [-]Integrate Fraud Protection from Group-IB into NewDot[/-][+][Due for payment 2025-10-01] Integrate Fraud Protection from Group-IB into NewDot[/+]on Sep 24, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.17-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
changed the title [-][Due for payment 2025-10-01] Integrate Fraud Protection from Group-IB into NewDot[/-][+]Integrate Fraud Protection from Group-IB into NewDot[/+]on Sep 25, 2025
The SDK is integrated and most events are already being tracked
We needed a new library in the App for hashing some sensitive data, like card numbers. That slowed us a bit but we have the approvals
We're dealing with some CORS issues on the desktop App. Group-IB found that the root cause is in their JS snippet, and we're waiting for them to provide a fixed version of it
Next Steps
Work on finishing all event tracking, now that we have approvals for adding the crypto library needed for hashing
Integrate the new js snippet when it is provided by Group-IB team
Activity
cristipaval commentedon Aug 13, 2025
Update
group-ib-fpmodule into the mobile App and successfully built the Hybrid app and standalone App on both Android and iOS platforms.Next Steps
cristipaval commentedon Aug 19, 2025
Update
cristipaval commentedon Aug 22, 2025
Update
cristipaval commentedon Aug 25, 2025
Update
QUERY_ALLPACKAGESpermission that has to be justified in Google Play. Details here39 remaining items
[-]Integrate Fraud Protection from Group-IB into NewDot[/-][+][Due for payment 2025-10-01] Integrate Fraud Protection from Group-IB into NewDot[/+]melvin-bot commentedon Sep 24, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Sep 24, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.17-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-10-01. 🎊
[-][Due for payment 2025-10-01] Integrate Fraud Protection from Group-IB into NewDot[/-][+]Integrate Fraud Protection from Group-IB into NewDot[/+]cristipaval commentedon Sep 25, 2025
Update
Next Steps
cristipaval commentedon Sep 29, 2025
The integration is done. I am still working on some follow-up issues with Group-IB, but I'm creating issues on the go when needed. Closing this one.