# New "Account Compromised" Messaging

**URL:** <https://mpsocial.com/t/new-account-compromised-messaging/75502>\
**Category:** Instagram Marketing\
**Created:** [July 18, 2019, 3:57pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502 "2019-07-18T15:57:16Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![koin3190](https://mpsocial.com/user_avatar/mpsocial.com/koin3190/32/33456_2.png) [@koin3190](https://mpsocial.com/u/koin3190)\
**Post date:** [July 18, 2019, 3:57pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/1 "2019-07-18T15:57:16Z")

</div>

![image1](https://mpsocial.com/uploads/default/original/3X/d/a/da8e719790ee9f60e9e04bdb19215ab0eb1d2817.jpeg)

Curious to see how this will shake out.

---

<div class="post-metadata">

**Author:** ![DonPapo](https://mpsocial.com/user_avatar/mpsocial.com/donpapo/32/34455_2.png) [@DonPapo](https://mpsocial.com/u/DonPapo)\
**Post date:** [July 18, 2019, 3:59pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/2 "2019-07-18T15:59:47Z")

</div>

Had it on few accounts, just switch account and dont automate it for 48h. Then start slowly and thats it… I got these msgs over few times on several accounts… Hope it helps!

---

<div class="post-metadata">

**Author:** ![runninx77](https://mpsocial.com/user_avatar/mpsocial.com/runninx77/32/34251_2.png) [@runninx77](https://mpsocial.com/u/runninx77)\
**Post date:** [July 18, 2019, 8:23pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/3 "2019-07-18T20:23:27Z")

</div>

Are you automating? (probably yes), so rest the account like @DonPapo said. Also what kind of proxies are you using, how many accounts per proxy, are you doing actions in EB or through API?

---

<div class="post-metadata">

**Author:** ![koin3190](https://mpsocial.com/user_avatar/mpsocial.com/koin3190/32/33456_2.png) [@koin3190](https://mpsocial.com/u/koin3190)\
**Post date:** [July 18, 2019, 8:28pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/4 "2019-07-18T20:28:43Z")

</div>

Yes I’m automating lol  
Am resting the account(s) in question  
Mainly API right now, keep running into temp blocks via EB

---

<div class="post-metadata">

**Author:** ![runninx77](https://mpsocial.com/user_avatar/mpsocial.com/runninx77/32/34251_2.png) [@runninx77](https://mpsocial.com/u/runninx77)\
**Post date:** [July 18, 2019, 8:55pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/5 "2019-07-18T20:55:57Z")

</div>

Can you post your settings?

---

<div class="post-metadata">

**Author:** ![Tritan84](https://mpsocial.com/letter_avatar_proxy/v4/letter/t/d9b06d/32.png) [@Tritan84](https://mpsocial.com/u/Tritan84)\
**Post date:** [July 19, 2019, 12:32pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/6 "2019-07-19T12:32:48Z")

</div>

Received this message. Changed password. Applied password to automation tool. Did not rest it. I’m blocked from liking, following, posting until the 23rd. I’ll be much more cautious with automation when the block is lifted. I’m a complete noob though

---

<div class="post-metadata">

**Author:** ![Gaevintt](https://mpsocial.com/user_avatar/mpsocial.com/gaevintt/32/35074_2.png) [@Gaevintt](https://mpsocial.com/u/Gaevintt)\
**Post date:** [July 19, 2019, 12:45pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/7 "2019-07-19T12:45:37Z")

</div>

I have some friends who have receive this message but Idk I am not receive any message like this.  
Even though my accounts are running on Jarvee 😉

---

<div class="post-metadata">

**Author:** ![IIS](https://mpsocial.com/letter_avatar_proxy/v4/letter/i/c77e96/32.png) [@IIS](https://mpsocial.com/u/IIS)\
**Post date:** [July 27, 2019, 4:56pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/8 "2019-07-27T16:56:11Z")

</div>

> [@Gaevintt](#):
>
> I have some friends who have receive this message but Idk I am not receive any message like this.  
> Even though my accounts are running on Jarvee 😉

Hi, what do you mean by switch account?

---

<div class="post-metadata">

**Author:** ![Ryan\_Hyndman](https://mpsocial.com/user_avatar/mpsocial.com/ryan_hyndman/32/39247_2.png) [@Ryan\_Hyndman](https://mpsocial.com/u/Ryan_Hyndman)\
**Post date:** [July 31, 2019, 3:47pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/9 "2019-07-31T15:47:24Z")

</div>

I just got this message today. Turning off tool for 48hrs before starting again.

---

<div class="post-metadata">

**Author:** ![redlightmeansgo](https://mpsocial.com/letter_avatar_proxy/v4/letter/r/ccd318/32.png) [@redlightmeansgo](https://mpsocial.com/u/redlightmeansgo)\
**Post date:** [July 31, 2019, 5:07pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/10 "2019-07-31T17:07:57Z")

</div>

I got the messaged, changed the password, resumed all my settings like normal. Nothing different happened every time.

---

<div class="post-metadata">

**Author:** ![embraceone](https://mpsocial.com/user_avatar/mpsocial.com/embraceone/32/34092_2.png) [@embraceone](https://mpsocial.com/u/embraceone)\
**Post date:** [July 31, 2019, 5:12pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/11 "2019-07-31T17:12:53Z")

</div>

If you see this message, don’t wait until you’ve been banned from all actions for a week to do something about it. Rather take full precautionary measures before you destroy your account’s trust rating any further.

---

<div class="post-metadata">

**Author:** ![koin3190](https://mpsocial.com/user_avatar/mpsocial.com/koin3190/32/33456_2.png) [@koin3190](https://mpsocial.com/u/koin3190)\
**Post date:** [July 31, 2019, 5:21pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/12 "2019-07-31T17:21:29Z")

</div>

> [@embraceone](#):
>
> If you see this message, don’t wait until you’ve been banned from all actions for a week to do something about it. Rather take full precautionary measures before you destroy your account’s trust rating any further.

> [@redlightmeansgo](#):
>
> I got the messaged, changed the password, resumed all my settings like normal. Nothing different happened every time.

Perhaps this means that the AC message the 7 day block don’t always come hand in hand.

---

<div class="post-metadata">

**Author:** ![IIS](https://mpsocial.com/letter_avatar_proxy/v4/letter/i/c77e96/32.png) [@IIS](https://mpsocial.com/u/IIS)\
**Post date:** [August 2, 2019, 9:29am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/13 "2019-08-02T09:29:40Z")

</div>

So what do you think we need to do? I received this block on 4 accounts … the actions were these:  
1 -30/40 F per day  
2 -60/70 F per day  
3 -125/135 F per day  
4 -180/90 F per day

Customers have changed Psw and I’m having the account rest for 2 days. After?

---

<div class="post-metadata">

**Author:** ![embraceone](https://mpsocial.com/user_avatar/mpsocial.com/embraceone/32/34092_2.png) [@embraceone](https://mpsocial.com/u/embraceone)\
**Post date:** [August 2, 2019, 10:11am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/14 "2019-08-02T10:11:38Z")

</div>

Reset Device IDs, Change Proxies and potentially ISP if you can. Re-login, wait 48 hours with only viewing activity. The gap between your minimum and maximum daily actions seems too low to me.

---

<div class="post-metadata">

**Author:** ![GramMaster](https://mpsocial.com/user_avatar/mpsocial.com/grammaster/32/41213_2.png) [@GramMaster](https://mpsocial.com/u/GramMaster)\
**Post date:** [August 2, 2019, 10:35am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/15 "2019-08-02T10:35:07Z")

</div>

what proxy are you using?

---

<div class="post-metadata">

**Author:** ![IIS](https://mpsocial.com/letter_avatar_proxy/v4/letter/i/c77e96/32.png) [@IIS](https://mpsocial.com/u/IIS)\
**Post date:** [August 2, 2019, 11:52am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/16 "2019-08-02T11:52:02Z")

</div>

1- When you say you change proxies you intend to change IP address?  
2 - How do I change ISP? Should I ask for proxies that “run” on another operator’s sim?

Anyway thanks for the info

---

<div class="post-metadata">

**Author:** ![IIS](https://mpsocial.com/letter_avatar_proxy/v4/letter/i/c77e96/32.png) [@IIS](https://mpsocial.com/u/IIS)\
**Post date:** [August 2, 2019, 11:53am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/17 "2019-08-02T11:53:37Z")

</div>

AirProxie…but I really don’t think it’s a problem of proxies

---

<div class="post-metadata">

**Author:** ![IIS](https://mpsocial.com/letter_avatar_proxy/v4/letter/i/c77e96/32.png) [@IIS](https://mpsocial.com/u/IIS)\
**Post date:** [August 2, 2019, 12:00pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/18 "2019-08-02T12:00:46Z")

</div>

The gap has worked until now on all accounts … widen the gap, such as 150/200?

---

<div class="post-metadata">

**Author:** ![Enguerran](https://mpsocial.com/user_avatar/mpsocial.com/enguerran/32/55303_2.png) [@Enguerran](https://mpsocial.com/u/Enguerran)\
**Post date:** [August 2, 2019, 1:24pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/19 "2019-08-02T13:24:47Z")

</div>

I have two clients who have this compromised status, one is living near my proxy DC location and the other one is living very far from my proxy location (he is traveling a lot).  
What I can say is that I have others clients that have a follow block while they live in the city where my proxies are located and some are living in the US while I’m located in Europe and don’t have any block.

It’s so fucked up 😕

---

<div class="post-metadata">

**Author:** ![Socially](https://mpsocial.com/user_avatar/mpsocial.com/socially/32/36469_2.png) [@Socially](https://mpsocial.com/u/Socially)\
**Post date:** [August 6, 2019, 12:14am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/20 "2019-08-06T00:14:31Z")

</div>

Getting hit with a lot of these right now… anyone else?

[Next page](https://mpsocial.com/t/new-account-compromised-messaging/75502.md?page=2)
