Skip to content

Integrate Fraud Protection from Group-IB into NewDot #68284

Closed

Description

@cristipaval

Problem

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.

Activity

  1. self-assigned this
    on Aug 11, 2025
  2. added theissue type on Aug 11, 2025
  3. cristipaval commented on Aug 13, 2025

    @cristipaval
    ContributorAuthor

    Update

    • I integrated the group-ib-fp module into the mobile App and successfully built the Hybrid app and standalone App on both Android and iOS platforms.
    • OldApp PR is ready for merge
    • 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
  4. cristipaval commented on Aug 19, 2025

    @cristipaval
    ContributorAuthor

    Update

    • PR with the SDK integration is in review, but the Hybrid iOS build fails. Asked for help here
    • PR with the events being sent to Fraud Protection backend is also up, but held on the above
  5. cristipaval commented on Aug 22, 2025

    @cristipaval
    ContributorAuthor

    Update

    • SDK is integrated in the App Bundle
    • PR with the event sending is still WIP due to some hiccups we're having on Android. I'm having a call with Group-IB team today to get past it
  6. cristipaval commented on Aug 25, 2025

    @cristipaval
    ContributorAuthor

    Update

    • The PR with the SDK integration was reverted due to the QUERY_ALLPACKAGES permission that has to be justified in Google Play. Details here
    • I had a call with Group-IB to investigate why the event logging didn't work. It was an IP rule misconfiguration on their side
    • Group-IB provided me with documentation on how to comply with Google requirements for using that permission
    • The PR with the event logging is now on HOLD until we integrate the SDK again
  7. 39 remaining items

  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Sep 24, 2025
  9. 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
  10. melvin-bot commented on Sep 24, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  11. melvin-bot commented on Sep 24, 2025

    @melvin-bot

    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. 🎊

  12. added and removed
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on Sep 25, 2025
  13. 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
  14. cristipaval commented on Sep 25, 2025

    @cristipaval
    ContributorAuthor

    Update

    • 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
  15. cristipaval commented on Sep 29, 2025

    @cristipaval
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

DailyKSv2Fire-CleanupSomething needs to be done after a fireReviewingHas a PR in review

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions