EyeFly Digital has been dealing with compounding Meta platform issues since September 2025 — a $5k account hack, trademark violation warnings, personal account disablement, a page creation block, and an earlier ad restriction. This is the executive agenda for today's call with Trevor.
"yo our ad account got hacked we just got waxed for $5k" — first alert, Apr 9 morning, confirms breach and dollar amount
Unauthorized plant/equipment ads visible in EyeFly's Ads Manager. Campaigns created and running without authorization.
BM activity log showing unauthorized actions taken by Giuseppe De Maio account. Timestamps confirm breach window.
Fraudulent partner listed in EyeFly's BM. "Akash Punnoose" is not affiliated with EyeFly — added by bad actor during compromise.
Fraudulent charges on EyeFly's payment method for Black Hills Concrete campaigns. Dispute reference visible in billing history.
Two-factor authentication confirmed enabled at time of breach — confirms attacker bypassed 2FA. Breach vector requires Meta security investigation.
| Ask | Detail | Priority |
|---|---|---|
| Confirm dispute status + refund timeline | Is the $5,046 chargeback approved? When does the refund process? | P0 |
| Breach vector investigation | How did actor bypass active 2FA? Was a Meta employee or system involved? | P0 |
| Giuseppe De Maio identity | Can Meta provide info on this account for potential legal action? | P2 |
| Ask | Detail | Priority |
|---|---|---|
| Pull full violation log | Every IP/TM flag on the EyeFly BM — dates, content IDs, status (active vs. cleared) | P1 |
| Clearance process | How do we formally resolve/clear each active warning? What's the process? | P1 |
| Proactive review | Can Meta review our creative templates before launch to prevent future flags? | P2 |
Original Meta notification showing account disabled. Reason cited is vague — no specific policy violation clearly stated.
Confirmation that appeal was submitted through Meta's standard review process. Reference number on file.
Subsequent replies from Meta support — no substantive resolution, appeal still under review with no timeline given.
| Ask | Detail | Priority |
|---|---|---|
| Escalate disable appeal internally | Standard appeals are stalled — need Trevor to push through Meta's internal team for actual review | P0 |
| Root cause disclosure | What specific policy triggered the disable? Need to understand to prevent recurrence | P1 |
| BM admin redundancy | Can we add a verified secondary admin to reduce single-account dependency going forward? | P2 |
| Ask | Detail | Priority |
|---|---|---|
| Lift the page creation block | Provide EyeFly's BM ID to Meta's team and request immediate block removal | P1 |
| Identify the trigger | Was this caused by volume, a policy flag, or account age? Need to understand to prevent recurrence | P1 |
| Agency allowlist | As a scaling agency (28 → 60+ clients), can EyeFly be whitelisted for higher page creation volume? | P2 |
| Ask | Detail | Priority |
|---|---|---|
| Confirm restriction is fully cleared | Is this event still on our account's health record? Does it factor into current policy enforcement? | P2 |
| Account health score | What is EyeFly's current account health/trust score? What's needed to improve it? | P2 |