# 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:** 3

<div class="post-metadata">

**Author:** ![Agent242](https://mpsocial.com/user_avatar/mpsocial.com/agent242/32/33992_2.png) [@Agent242](https://mpsocial.com/u/Agent242)\
**Post date:** [August 6, 2019, 3:45am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/41 "2019-08-06T03:45:02Z")

</div>

So temporary blocks lead into Account Compromised message.

How can we stop “temp blocks”?

---

<div class="post-metadata">

**Author:** ![AlphaPaul](https://mpsocial.com/user_avatar/mpsocial.com/alphapaul/32/32286_2.png) [@AlphaPaul](https://mpsocial.com/u/AlphaPaul)\
**Post date:** [August 6, 2019, 7:26am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/42 "2019-08-06T07:26:26Z")

</div>

It would be really interesting to know what you’re gonna do with those clients receiveng the compromised message

---

<div class="post-metadata">

**Author:** ![Typhoon](https://mpsocial.com/user_avatar/mpsocial.com/typhoon/32/32538_2.png) [@Typhoon](https://mpsocial.com/u/Typhoon)\
**Post date:** [August 6, 2019, 8:18am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/43 "2019-08-06T08:18:44Z")

</div>

First of all stop the account for at least 3 days.

---

<div class="post-metadata">

**Author:** ![andrejo](https://mpsocial.com/user_avatar/mpsocial.com/andrejo/32/37064_2.png) [@andrejo](https://mpsocial.com/u/andrejo)\
**Post date:** [August 6, 2019, 8:47am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/44 "2019-08-06T08:47:14Z")

</div>

OK, most of our clients started getting **Account Compromised** message

all on 4g proxies, god/like settings with proper warmup.

What is the process you suggest after changing password? When do you opt for first interactions?

---

<div class="post-metadata">

**Author:** ![Typhoon](https://mpsocial.com/user_avatar/mpsocial.com/typhoon/32/32538_2.png) [@Typhoon](https://mpsocial.com/u/Typhoon)\
**Post date:** [August 6, 2019, 8:53am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/45 "2019-08-06T08:53:09Z")

</div>

I sad to my clients to change their password from themselfs ( I don’t like to use Jarvee/MP on this operations). I’m planning to start very slowly and do some test in minor accounts in 3 days

---

<div class="post-metadata">

**Author:** ![Hank9991](https://mpsocial.com/user_avatar/mpsocial.com/hank9991/32/41004_2.png) [@Hank9991](https://mpsocial.com/u/Hank9991)\
**Post date:** [August 6, 2019, 10:45am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/46 "2019-08-06T10:45:33Z")

</div>

do for one or two weeks only like and story viewing , commenting what i am seeing is that follow is triggering the hard block for 7 days

---

<div class="post-metadata">

**Author:** ![andrejo](https://mpsocial.com/user_avatar/mpsocial.com/andrejo/32/37064_2.png) [@andrejo](https://mpsocial.com/u/andrejo)\
**Post date:** [August 6, 2019, 10:53am UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/47 "2019-08-06T10:53:40Z")

</div>

we are planning on doing ¨7 days completely off  
then start a brand new warmup - story views - then follows (after 3-5 days)

---

<div class="post-metadata">

**Author:** ![Isedo](https://mpsocial.com/user_avatar/mpsocial.com/isedo/32/36335_2.png) [@Isedo](https://mpsocial.com/u/Isedo)\
**Post date:** [August 6, 2019, 12:55pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/48 "2019-08-06T12:55:33Z")

</div>

Seems like a general problem. In Uk, Germany and Italy a lot of users are having issues logging in, posting and using IG at all. Maybe it is not related to automations?

By the way 90% of my clients (20) get this issue.

---

<div class="post-metadata">

**Author:** ![Tyson](https://mpsocial.com/letter_avatar_proxy/v4/letter/t/b4bc9f/32.png) [@Tyson](https://mpsocial.com/u/Tyson)\
**Post date:** [August 6, 2019, 1:20pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/49 "2019-08-06T13:20:54Z")

</div>

90% of my 100 clients are getting this

---

<div class="post-metadata">

**Author:** ![Isedo](https://mpsocial.com/user_avatar/mpsocial.com/isedo/32/36335_2.png) [@Isedo](https://mpsocial.com/u/Isedo)\
**Post date:** [August 6, 2019, 1:27pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/50 "2019-08-06T13:27:24Z")

</div>

I think it is not related to automations. I think it’s IG which is messing around.  
They are killing “likes”, they are rolling out the possibility to post from the Creator Studio and rolling out several monetization features for videos.

What do you think?

---

<div class="post-metadata">

**Author:** ![Tyson](https://mpsocial.com/letter_avatar_proxy/v4/letter/t/b4bc9f/32.png) [@Tyson](https://mpsocial.com/u/Tyson)\
**Post date:** [August 6, 2019, 1:36pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/51 "2019-08-06T13:36:11Z")

</div>

I think it’s definitely related to automations. As the msg clears says the account share password to a growth company. It’s cant be more clear than that.

---

<div class="post-metadata">

**Author:** ![Isedo](https://mpsocial.com/user_avatar/mpsocial.com/isedo/32/36335_2.png) [@Isedo](https://mpsocial.com/u/Isedo)\
**Post date:** [August 6, 2019, 1:39pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/52 "2019-08-06T13:39:51Z")

</div>

Yes but Jarvee claims, for example, that they are not seen by IG as a growth company. which is your opinion?

---

<div class="post-metadata">

**Author:** ![andrejo](https://mpsocial.com/user_avatar/mpsocial.com/andrejo/32/37064_2.png) [@andrejo](https://mpsocial.com/u/andrejo)\
**Post date:** [August 6, 2019, 2:51pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/53 "2019-08-06T14:51:36Z")

</div>

please bro you cant be serious that you actually still believe this

the moment you connect your account to Jarvee/MP IG knows that very second.

---

<div class="post-metadata">

**Author:** ![Isedo](https://mpsocial.com/user_avatar/mpsocial.com/isedo/32/36335_2.png) [@Isedo](https://mpsocial.com/u/Isedo)\
**Post date:** [August 6, 2019, 5:44pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/54 "2019-08-06T17:44:41Z")

</div>

Yeah maybe u’re right. So does this means using Jarvee is over?

---

<div class="post-metadata">

**Author:** ![vanmatte](https://mpsocial.com/user_avatar/mpsocial.com/vanmatte/32/32949_2.png) [@vanmatte](https://mpsocial.com/u/vanmatte)\
**Post date:** [August 6, 2019, 11:08pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/55 "2019-08-06T23:08:45Z")

</div>

If after the “Account compromised” message you are getting the 7 days hard block (no likes, comments, post), I created this topic to talk about it.  
Hope we can find a solution ASAP.

> [@Hard action block (no likes, no comments, no follows, no posting) for 7 days](https://mpsocial.com/t/hard-action-block-no-likes-no-comments-no-follows-no-posting-for-7-days/75183):
>
> Ok guys, now I have a very big problem on my personal account. I am blocked for 7 days with liking, comments, follows and posting. Before starting: Botting this account by 2 years with Jarvee Account created in 2011, always used Never had problems or blocks (just the 6000/30) Using without proxy but with my home WiFi (only this account on my WiFi) Creator account 190 follows for day, 190 unfollows for day, 300 likes for day 8 hours of sleep time What happened: It all started last week…

---

<div class="post-metadata">

**Author:** ![jpgrowthhack](https://mpsocial.com/letter_avatar_proxy/v4/letter/j/85f322/32.png) [@jpgrowthhack](https://mpsocial.com/u/jpgrowthhack)\
**Post date:** [August 7, 2019, 10:08pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/56 "2019-08-07T22:08:18Z")

</div>

I know I saw this somewhere but couldn’t find it when I searched. Sorry if it is a repeat (I’m sure it is, but couldn’t find anyone who got this exact message)

I got the attached screenshot as a message using very conservative warm upsettings for an account I grew through F/UF. It had been dormant for a few months but I started it up again using Jarvee again and saw this error.

I am now using 4g proxies (wasn’t before)

My question is, what should I do? How long do I wait before resuming efforts? Any settings I should change?

Thanks for your help!

 ![IG](https://mpsocial.com/uploads/default/original/3X/b/6/b66a910545e842aab84c0dae81287f157ae5b91e.png)

---

<div class="post-metadata">

**Author:** ![madkap](https://mpsocial.com/user_avatar/mpsocial.com/madkap/32/33856_2.png) [@madkap](https://mpsocial.com/u/madkap)\
**Post date:** [August 7, 2019, 10:19pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/57 "2019-08-07T22:19:15Z")

</div>

https://tenor.com/embed/9265562?playertype=card

---

<div class="post-metadata">

**Author:** ![AbuBakr](https://mpsocial.com/user_avatar/mpsocial.com/abubakr/32/31973_2.png) [@AbuBakr](https://mpsocial.com/u/AbuBakr)\
**Post date:** [August 7, 2019, 10:45pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/58 "2019-08-07T22:45:20Z")

</div>

there is a topic about that already , Here you go buddy :  
[https://mpsocial.com/t/massive-account-compromised-wave/76992](https://mpsocial.com/t/massive-account-compromised-wave/76992)

---

<div class="post-metadata">

**Author:** ![Szr](https://mpsocial.com/user_avatar/mpsocial.com/szr/32/40986_2.png) [@Szr](https://mpsocial.com/u/Szr)\
**Post date:** [August 7, 2019, 10:49pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/59 "2019-08-07T22:49:33Z")

</div>

Oh damn. Instagram is catching up 😝

---

<div class="post-metadata">

**Author:** ![jpgrowthhack](https://mpsocial.com/letter_avatar_proxy/v4/letter/j/85f322/32.png) [@jpgrowthhack](https://mpsocial.com/u/jpgrowthhack)\
**Post date:** [August 7, 2019, 10:51pm UTC](https://mpsocial.com/t/new-account-compromised-messaging/75502/60 "2019-08-07T22:51:56Z")

</div>

Thank you! Sorry I couldn’t find it for some reason when I searched.

I guess I don’t have access to that post 😕

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

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