879
Of course , this is not real Google Docs – the attacker has simply named his “ application ” Google Docs – this can be verified by clicking on the Google Docs text where the real web site behind this and developer info is shown : Obviously , once you allow access it is game over - the attacker probably uses the phishied Gmail account to further distribute phishing e-mails - we 'll see if we can get more details .
 ( phishing: has simply named,  the attacker: attacker, Google Docs: trusted entity, his “ application ”: trusted entity) 
Locate the role in the text that participated in the event based on the event type and return it in the event list. 
 Option: Event type: phishing, data breach, ransom, discover vulnerability, patch vulnerability, Arguments type: vulnerable system, capabilities, vulnerability, number of victim, issues addressed, compromised data, damage amount, common vulnerabilities and exposures, victim, patch number, number of data, tool, discoverer, time, purpose, place, payment method, releaser, vulnerable system version, attacker, supported platform, patch, price, vulnerable system owner, trusted entity, attack pattern. 
Text: {0} 
Answer:
 ( phishing: has simply named,  the attacker: attacker, Google Docs: trusted entity, his “ application ”: trusted entity) 