Datasets:

huy-nh-2000

/

instructUIE

like 0

[]

{ "id": "3737", "sentence": "The 2016 Ransomware Report released by 360 Security Center lately presents that : – 4.9 million computers were attacked in China – 56,000 ransomware infections worldwide only in March 2016 – $ 1 billion dollar source of income for cyber criminals estimated by FBI – Almost half of organizations have been hit with ransomware In January 2016 , three Indian banks ’ and a pharmaceutical company ’s computer systems were infected by ransomware .", "label": " ( ransom: were infected, computer systems: victim, ransomware: tool, pharmaceutical company: victim, Indian banks: victim, January 2016: time) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( ransom: were infected, computer systems: victim, ransomware: tool, pharmaceutical company: victim, Indian banks: victim, January 2016: time) " }

[]

{ "id": "3738", "sentence": "The attacker asked for 1 bitcoin ( about $ 905 ) for each infected computer , and then used unprotected desktop interface to infect other connected computers from remote .", "label": " ( ransom: asked for, 1 bitcoin: price, attacker: attacker, $ 905: price, infected computer: victim, unprotected desktop interface: victim, infect other connected computers from remote: attack pattern) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( ransom: asked for, 1 bitcoin: price, attacker: attacker, $ 905: price, infected computer: victim, unprotected desktop interface: victim, infect other connected computers from remote: attack pattern) " }

[]

{ "id": "3739", "sentence": "February 5th 2016 , Hollywood Presbyterian Medical Center paid a $ 17,000 ransom in bitcoin to a hacker who seized control of the hospital ’s computer systems and would give back access only when the money was paid .", "label": " ( ransom: paid, February 5th 2016: time, Hollywood Presbyterian Medical Center: victim, $ 17,000: price, in bitcoin: payment method, hacker: attacker, seized control: attack pattern, computer systems: victim, hospital: victim) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( ransom: paid, February 5th 2016: time, Hollywood Presbyterian Medical Center: victim, $ 17,000: price, in bitcoin: payment method, hacker: attacker, seized control: attack pattern, computer systems: victim, hospital: victim) " }

[]

{ "id": "3740", "sentence": "The hacker took control of the intranet and servers , and asked for 20 bitcoin .", "label": " ( ransom: asked for, servers: victim, intranet: victim, hacker: attacker, 20 bitcoin: price, took control: attack pattern) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( ransom: asked for, servers: victim, intranet: victim, hacker: attacker, 20 bitcoin: price, took control: attack pattern) " }

[]

{ "id": "3741", "sentence": "These school ended up paying the anonymous hacker $ 8,500 to get their IT systems back .", "label": " ( ransom: ended up paying, hacker: attacker, $ 8,500: price, school: victim, IT systems: victim) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( ransom: ended up paying, hacker: attacker, $ 8,500: price, school: victim, IT systems: victim) " }

[]

{ "id": "3742", "sentence": "Once users activated the file attached in the email , their files were encrypted and had to pay the distributor a certain ransom to decrypt these files .", "label": " ( ransom: had to pay, their files were encrypted: attack pattern, the distributor: attacker, users: victim) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( ransom: had to pay, their files were encrypted: attack pattern, the distributor: attacker, users: victim) " }

[]

{ "id": "3743", "sentence": "In October , 2016 , 277 ransomware attacks were reported to Government Computer Emergency Response Team in Hong Kong , China .", "label": " ( ransom: ransomware attacks, October , 2016: time, Hong Kong: place, China: place) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( ransom: ransomware attacks, October , 2016: time, Hong Kong: place, China: place) " }

[]

{ "id": "3744", "sentence": "Most of the malware were hidden in email attachments and disguised as bills or receipts to trick users to click .", "label": " ( phishing: disguised as, bills: trusted entity, receipts: trusted entity, email attachments: tool, the malware: tool) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( phishing: disguised as, bills: trusted entity, receipts: trusted entity, email attachments: tool, the malware: tool) " }

[]

{ "id": "3745", "sentence": "November 2016 , San Francisco public transportation system Muni was hacked and requested for a $ 73,000 ransom in bitcoin to get back encrypted data .", "label": " ( ransom: requested for, $ 73,000: price, in bitcoin: payment method, San Francisco public transportation system Muni: victim, November 2016: time) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( ransom: requested for, $ 73,000: price, in bitcoin: payment method, San Francisco public transportation system Muni: victim, November 2016: time) " }

[]

{ "id": "3746", "sentence": "SFMTA ( The San Francisco Municipal Transportation Authority ) refused to pay the ransom and shut down the fair system .", "label": " ( ransom: refused to pay, SFMTA ( The San Francisco Municipal Transportation Authority ): victim, the fair system: victim) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( ransom: refused to pay, SFMTA ( The San Francisco Municipal Transportation Authority ): victim, the fair system: victim) " }

[]

{ "id": "3747", "sentence": "The Russian firm is said to have extensive technical experience in security vulnerabilities of supervisory control and data acquisition systems that are used to remotely control critical infrastructure .", "label": " ( discover vulnerability: said, security vulnerabilities: vulnerability, supervisory control and data acquisition systems: vulnerable system, remotely control critical infrastructure: capabilities, The Russian firm: discoverer) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( discover vulnerability: said, security vulnerabilities: vulnerability, supervisory control and data acquisition systems: vulnerable system, remotely control critical infrastructure: capabilities, The Russian firm: discoverer) " }

[]

{ "id": "3748", "sentence": "The recent political furor over state sponsored hacking took an ugly and dangerous turn , on the morning of December 30th when a tiny Vermont electric utility reported that Grizzly Steppe – the spear - fishing process used to access DNC emails – had been found on one of their systems .", "label": " ( data breach: access, DNC emails: compromised data, the spear - fishing process: attack pattern, Grizzly Steppe: attack pattern) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( data breach: access, DNC emails: compromised data, the spear - fishing process: attack pattern, Grizzly Steppe: attack pattern) " }

[]

{ "id": "3749", "sentence": "Two years prior to the first Ukraine incident , hackers began attempting to acquire legitimate login credentials by hacking non-operational systems at Ukrainian utilities – systems very much like Burlington Electric ’s laptop .", "label": " ( data breach: acquire, login credentials: compromised data, hackers: attacker, Two years prior: time) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( data breach: acquire, login credentials: compromised data, hackers: attacker, Two years prior: time) " }

[]

{ "id": "3750", "sentence": "According to a Booz Allen analysis , spear - phishing emails containing weaponized Microsoft Word , Excel , and PowerPoint files , exactly the type of files typically found on laptop computers , were sent to Ukraine electric utility employees as early as May 2014 .", "label": " ( phishing: were sent to, May 2014: time, Ukraine electric utility employees: victim, spear - phishing emails: tool) ", "instruction": "Locate the role in the text that participated in the event based on the event type and return it in the event list. \n 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. \nText: {0} \nAnswer:", "ground_truth": " ( phishing: were sent to, May 2014: time, Ukraine electric utility employees: victim, spear - phishing emails: tool) " }