IRM Policies part1

Our current policy framework for identity misrepresentations include:

• Fake Profile

  Shell Account

  Secondhand Account

  Account Sharing

  Fraudulent Subcontracting

  Khabarovsk Group

  FR13

• Fake Profile

  Shell Account

  Secondhand Account

  Account Sharing

  Fraudulent Subcontracting

• Fake Profile

  Shell Account

  Secondhand Account

  Fraudulent Subcontracting

  Khabarovsk Group

  FR13

• Fake Profile

  Shell Account

  Secondhand Account

  Account Sharing

  Fraudulent Subcontracting

  Khabarovsk Group

Answer explanation

Reference: https://url.upwork.com/_012VFnDWwxRtqNmjawI3vsG2d-Z1X1Io1h

These are accounts that are created for the purpose of testing our detection thresholds and/or age the account to make it seem more trustworthy then sell it to other users

• Shell Account

• Fake Profile

• Secondhand Account

• Account Sharing

Answer explanation

Reference: https://url.upwork.com/_012VFnDWwxRtoq1Gvkn-1Sh6XE_aHTLBXR

A fake profile photo is enough evidence to suspend an account for fake profile

• True

• False

Answer explanation

Reference: https://url.upwork.com/_012VFnDWwxRtoq3doq41ULG601tx7Fiu7z

When suspending for Fake Profile, we should always include the 490-IDV Required signal

• True

• False

Answer explanation

Reference: https://url.upwork.com/_012VFnDWwxRtqvyMWPoCPXPXGBNJi5IpAx

The following can be considered as evidence to suspend for Fake Profile. Select all that apply

• Profile blurb is gibberish

• Fake address

• Use of stock photo

• Multiple logins with no other actions

• Fake ID (au10tix)

Answer explanation

Reference: https://url.upwork.com/_012VFnDWwxRtp5O-d3ooYn64KBLLjOxHRj

We do not always have to include the 452 - Non-delivery Fraud Ring tag on a Shell Account suspension

• True

• False

Answer explanation

Reference: https://url.upwork.com/_012VFnDWwxRtod7kYZ-I3ouOvDuaJcRl90

A ticket escalation is sent to IRM for possible secondhand account. What information on the account should we check that it is correctly escalated for this violation?

• The account should be ID-badged and has some proposals sent

• The account may not be ID-badged yet but has some proposals sent

• The account should not be ID-badged yet and no proposals sent

• The account is ID-badged but has no proposals sent yet

Answer explanation

Reference: https://url.upwork.com/_012VFnDWwxRto3Sb3-yduAAwmYK9ipiEa5

When the registered name is different from the current profile name, we should immediately consider this as an evidence of Secondhand account.

• True

• False

Answer explanation

Reference: https://url.upwork.com/_012VFnDWwxRtrnXCrlWkhPixqcZaWAgdBc

The Identity Ops team escalated a ticket informing us that the user wants to change his account name.  When can we allow the team to have the user change his profile name?

• When there is no evidence of ASH or SHA and the user is not ID Badged yet.

• When there is evidence of ASH or SHA and the user is ID Badged.

• When there is no evidence of ASH or SHA but the user is ID Badged.

• When there is evidence of ASH or SHA and the user is not ID Badged yet

Answer explanation

Reference: https://url.upwork.com/_012VFnDWwxRtpGDDTL7lER_ugSLcpVPCff

What evidence can we consider as "exclusive" for Account Sharing and not Fraudulent Subcontracting? Select all that apply

• Use of multiple devices

• Multiple email handles and more than 1 github provided in MC

• Multiple UPMs with different names

• Shares the work with others

Answer explanation

Reference: https://url.upwork.com/_012VFnDWwxRtrYykRVc-mZnH_8sMsT_5gF