CiscoCISCO-THREAT-29776Threat Outbreak Alert: Fake Bank Payment Transfer Notification Email Messages on September 25, 2014
Low
Alert ID:
29776
First Published:
2013 June 25 14:23 GMT
Last Updated:
2014 September 25 19:02 GMT
Version:
49
Summary
- Cisco Security has detected significant activity related to spam email messages that claim to contain a bank payment transfer notification for the recipient. The text in the email message attempts to convince the recipient to open the attachment and view the details. However, the .rar attachment contains a malicious .scr file that, when executed, attempts to infect the system with malicious code.
Email messages that are related to this threat (RuleID6369 and RuleID6396KVR) may contain any of the following files:
> TT Copy.rar
TT Copy.scr
Remittance Swift Copy.rar
image.scr
TT COPY.exe
Payment Slip.rar
Payment Slip.scr
SWIFT COPY.exe
TT slip.exe
PAYMENT SLIP…rar
Slip.scr
payment.rar
payment.exe
Onk_Payment_slip.rar
Onk copy.exe
hope.exe
payment.com
SWIFT PAYMENT SLIP.rar
IMG_774_663.scr
$54020.rar
$54020.exe
payment details.rar
attachment.exe
payment.scr
Payment Receipt.rar
fox11.scr
THE PAYMENT.rar
THE PAYMENT.scr
Purchas Oreder.exe
fox12.scr
paymentdetails.rar
paymentdetails.exe
MY PAYMENT SLIPS.rar
THE PAYMENS.scr
Swift Copy.rar
weno.exe
tt copy 1.rar
po202.exe
swift copy.scr
SCAN COPY.rar
SCAN COPY.scr
PAYMENT SLIP.exe
Payment sclip.rar
NewOrder.exe
Paymentcopy.rar
Paymentcopy.exe
TT-COPY.rar
TT-COPY.exe
Purchase Order.rar
tt_copy.scr
Payment Swift Copy.rar
Scan000372.scr
Swift Payment Copy.rar
ictv.exe
TTpayment.rar
Paymentslip.exe
Payment Advice.rar
Payment Advice.exe
_img003.scr
Bank_Swift_Copy.rar
Bank_Swift_Copy.exe
paymentslip.rar
Payment 041B.rar
TT PAYMENT.rar
PAYMEN~1.EXE
Payment Receipt.exe
Payment.pdf.rar
PO0528~1.SCR
Scan Copy.exe
[email protected]
[email protected]
Comprovante_Deposito.rar
Comprovante_Deposito.com
PROFORMA INVOICE.rar
PROFORMA INVOICE.exe
BANK ACCT DETAILS.rar
BANK ACCT DETAILS.exe
Swift.rar
Swift.exe
_
The_ TT Copy.scr_ file in the TT Copy.rar attachment has a file size of 1,294,191 bytes. The MD5 checksum, which is a unique identifier of the executable, is the following string: 0xEA41DCDF537ACA08415F10243219BB56
The image.scr file in the Remittance Swift Copy.rar attachment has a file size of 192,512 bytes. The MD5 checksum is the following string: 0xF077A02F80B271992B3FFFD6390AFF03
The TT COPY.exe file in the TT COPY.rar attachment has a file size of 454,656 bytes. The MD5 checksum is the following string: 0x398E904C35521C560F69F831893AE911
The Payment Slip.scr file in the Payment Slip.rar attachment has a file size of 879,104 bytes. The MD5 checksum is the following string: 0xE950FD30D2EC80AB527DD3B3A6DFE57A
The_ SWIFT COPY.exe_ file in the SWIFT COPY.rar attachment has an approximate file size of 127,651 bytes. The MD5 checksum is the following string: e80768c57c5a9ada9bb6cfe6c7427551
The TT slip.exe file in the payment slip.rar attachment has a file size of 904,053 bytes. The MD5 checksum is the following string: 0x84B059D4D5A44CA0E1AF32D59D0DA48B
The_ Slip.scr _file in the _PAYMENT SLIP…rar _attachment has an approximate file size of 380,231 bytes. The MD5 checksum is not available.
The payment.exe in the payment.rar attachment has a file size of 1,295,556 bytes. The MD5 checksum is the following string: 0x886EC26577176E8C1401132457608F6F
A variant of the _PAYMENT SLIP.scr _file in the PAYMENT SLIP.rar attachment has a file size of 878,144 bytes. The MD5 checksum is the following string: 0x089FFEC1011F533F397F1663101FBA34
A third variant of the PAYMENT SLIP.scr file in the PAYMENT SLIP.rar attachment has a file size of 1,374,654 bytes. The MD5 checksum is the following string: 0xCE26C1098DBA14F6F3B897D7D967E758
A fourth variant of the PAYMENT SLIP.scr file in the PAYMENT SLIP.rar attachment has a file size of 852,544 bytes. The MD5 checksum is the following string: 0x04CB797364498C73984B9731D6EE910E
A variant of the SWIFT COPY.exe file in the SWIFT COPY.rar attachment has a file size of 263,383 bytes. The MD5 checksum is the following string: 0x779E6EFFCE74CB1A801FBB73E26F08DA
The Onk copy.exe file in the Onk_Payment_slip.rar attachment has a file size of 270,848 bytes. The MD5 checksum is the following string: 0x275D159AEC2BF1A09BAE2EE6D3B72420
The hope.exe file in the payment.rar attachment has a file size of 1,130,249 bytes. The MD5 checksum is the following string: 0xF5BE6F7D47C7847C2446F41714A08A30
The payment.com file in the payment.rar attachment has a file size of 986,624 bytes. The MD5 checksum is the following string: 0x4D4C0F6091561CAB54A0E8E799D12D0C
A fifth variant of the PAYMENT SLIP.scr file in the PAYMENT SLIP.rar attachment has a file size of 852,544 bytes. The MD5 checksum is the following string: 0x04CB797364498C73984B9731D6EE910E
The IMG_774_663.scr file in the SWIFT PAYMENT SLIP.rar attachment has a file size of 1,304,675 bytes. The MD5 checksum is the following string: 0x1E14F63AF7A5C59B85191FBE1109C07D
The $54020.exe file in the $54020.rar attachment has a file size of 193,736 bytes. The MD5 checksum is the following string: 0x2A6D355162290FD0DD7E6B8CDF2BB280
A sixth variant of the PAYMENT SLIP.scr file in the PAYMENT SLIP.rar attachment has a file size of 854,592 bytes. The MD5 checksum is the following string: 0xDC7FED0A7A5EEB69F3B456350954511F
The attachment.exe file in the payment details.rar attachment has a file size of 1,412,817 bytes. The MD5 checksum is the following string: 0x247296905E3C3A59AA8FEA0AF75A5E2C
The _payment.scr _file in the _payment.rar _attachment has a file size of 1,316,865 bytes. The MD5 checksum is the following string: 0x39743F6DED918223E731776AF8DAD63A
The _fox11.scr _file in the _Payment Receipt.rar _attachment has a file size of 835,136 bytes. The MD5 checksum is the following string: 0xACE3DD882EA6AB3F29172DA59853EF45
A variant of the payment.scr file in the payment.rar attachment has a file size of 855,616 bytes. The MD5 checksum is the following string: 0x1568F56DBBC4C6BEE24B2FC91F83CDF3
The _Purchas Oreder.exe _file in the Payment slip.rar attachment has a file size of 1,088,512 bytes. The MD5 checksum is the following string: 0xC690A6153C83F8949B9600918D3F0BFE
A seventh variant of the PAYMENT SLIP.scr file in the _PAYMENT SLIP.rar _attachment has a file size of 855,104 bytes. The MD5 checksum is the following string: 0xEAD8DB8A9AA2C609D1DA43BF39B14081
The fox12.scr in the Payment Slip.rar attachment has a file size of 838,208 bytes. The MD5 checksum is the following string: 0xA3DABEF95CF2916F210D4D637E5CCCBC
The_ paymentdetails.exe_ file in the paymentdetails.rar attachment has a file size of 371,712 bytes. The MD5 checksum is the following string: 0x57579EEAEECAAF44E2D0874DE4279226
The THE PAYMENS.scr in the MY PAYMENT SLIPS.rar file has a file size of 886,336 bytes. The MD5 checksum is the following string: 0x74B0B8578819C762D417A5B1B810CB94
The weno.exe in the Swift Copy.rar attachment has a file size of 610,816 bytes. The MD5 checksum is the following string: 0x8374574F3C3CE22ADA33CB6A72FB4288
The _po202.exe _file in the _tt copy 1.rar _attachment has a file size of 332,800 bytes. The MD5 checksum is the following string: 0x22AED6061B79CAD6861DCFAF1C228A15
The swift copy.scr file in the _swift copy.rar _attachment has a file size of 2,458,489 bytes. The MD5 checksum is the following string: 0x13A2FC1396399D6D4E904C4DF3ADCFF5
A third variant of the payment.scr file in the payment.rar attachment has a file size of 975,425 bytes. The MD5 checksum is the following string: 0xCAF1DACB59F24E43985F9BAF97464501
A variant of the _Payment.exe _file in the Payment.rar attachment has a file size of 573,952 bytes. The MD5 checksum is the following string: 0xEE33F6C616CBCAC2FF98ED6E95774270
The SCAN COPY.scr file in the SCAN COPY.rar attachment has a file size of 908,352 bytes. The MD5 checksum is the following string: 0xF9DB32BEEEC86EEA80D3E1166D6DC42C
The _PAYMENT SLIP.exe _file in the PAYMENT SLIP.rar attachment has a file size of 387,584 bytes. The MD5 checksum is the following string: 0xCE5E274A2B0AA8ACE61A48937F56CDF0
The NewOrder.exe file in the Payment sclip.rar attachment has a file size of 1,058,880 bytes. The MD5 checksum is the following string: 0xAE0735B2E6AB5F970C8848515D3530CE
An eighth variant of the Payment Slip.scr file in the Payment Slip.rar attachment has a file size of 870,464 bytes. The MD5 checksum is the following string: 0xA74CD15A7E036CEE2B87894C0E4F1BFE
The Paymentcopy.exe file in the Paymentcopy.rar attachment has a file size of 312,832 bytes. The MD5 checksum is the following string: 0x5A53E0551F4C8DBCF5C94B0892C88455
The TT-COPY.exe file in the TT-COPY.rar attachment has a file size of 596,992 bytes. The MD5 checksum is the following string: 0x60F3DB501AFB97710F12E7A7F42D9DB2
The tt_copy.scr file in the Purchase Order.rar attachment has a file size of 762,368 bytes. The MD5 checksum is the following string: 0xB13B88DC60EBE7832B8C0DFD51115028
A ninth variant of the payment slip.scr file in the payment slip.rar attachment has a file size of 841,280 bytes. The MD5 checksum is the following string: 0x5E88E001659DABC4A935A2B67D351989
The Scan000372.scr file in the Payment Swift Copy.rar attachment has a file size of 4,489,216 bytes. The MD5 checksum is the following string: 0x39608E514C9F6AE767736C5AAF4CFAA5
The ictv.exe file in the Swift Payment Copy.rar attachment has a file size of 515,892 bytes. The MD5 checksum is the following string: 0x35FC43A7F9164960FF169A45CA8799E5
The Paymentslip.exe file in the TTpayment.rar attachment has a file size of 983,003 bytes. The MD5 checksum is the following string: 0x2213914ACC4D9B14708C01AA535E7178
A third variant of the Swift Copy.exe file in the Swift Copy.rar attachment has a file size of 344,576 bytes. The MD5 checksum is the following string: 0x24F7A8497A7EFF82455B14EE89BB4DF8
The Payment Advice.exe file in the Payment Advice.rar attachment has a file size of 998,125 bytes. The MD5 checksum is the following string: 0x2B790E9C9E7CA1D5680204F386D7C155
A fourth variant of the THE PAYMENT.scr file in the THE PAYMENT.rar attachment has a file size of 857832 bytes. The MD5 checksum is the following string: 0x6DE4EBCA76F20FED27A4C501F950290D
The img003.scr file in the payment.rar attachment has a file size of 1,216,000 bytes. The MD5 checksum is the following string: 0x54C77D8E9C507A52DA2D0E0181EC0E4B
The Bank_Swift_Copy.exe file in the Bank_Swift_Copy.rar attachment has a file size of 389,120 bytes. The MD5 checksum is the following string: 0xA641BAE54D1B44F0E6F676FB4FBB17A9
A second variant of the Paymentslip.exe file in the_ payment.rar_ attachment has a file size of 455,680 bytes. The MD5 checksum is the following string: 0x6A8A8D15862104102561380B73A9032D
The Payment 041B.rar attachment has an approximate file size of 434,432 bytes. The MD5 checksum is not available.
The PAYMEN~1.EXE file in the TT PAYMENT.rar attachment has a file size of 442,368 bytes. The MD5 checksum is the following string: 0x4B3F0836C04E432E966818BE69548151
A variant of the PAYMEN~1.EXE file in the SCAN COPY.rar attachment has a file size of 409,600 bytes. The MD5 checksum is the following string: 0xBED16F47C884306731C1C08232561C3A
The_ Payment Receipt.exe _file in the Payment Receipt.rar attachment has a file size of 511,488 bytes. The MD5 checksum is the following string: 0x067F34EB498C89E9642D91889A9E8AB3
The PAYMEN~1.EXE file in the Payment Slip.rar attachment has a file size of 389,120 bytes. The MD5 checksum is the following string: 0x43E9A5FFF3C12B8E9152C153BF7DB2E2
The PO0528~1.SCR file in the_ Payment.pdf.rar_ attachment has a file size of 1,039,409 bytes. The MD5 checksum is the following string: 0xD9EB5CBC6592329925EC67E418B0B34D
The Scan Copy.exe in the Scan Copy.rar attachment has a file size of 484,352 bytes. The MD5 checksum is the following string: 0xFDE4068F322B43279DC53A6BE3BFFAF1
The [email protected] file in the [email protected] attachment has a file size of 1,324,544 bytes. The MD5 checksum is the following string: 0x777EFEBD1A1200FF090630258838D615
The Comprovante_Deposito.com file in the Comprovante_Deposito.rar attachment has a file size of 599,552 bytes. The MD5 checksum is the following string: 0xB9F55187A2406665F442862C2412EA56
The PROFORMA INVOICE.exe file in the PROFORMA INVOICE.rar attachment has a file size of 626,176 bytes. The MD5 checksum is the following string: 0xE16AD4F391620EF94EE3044FA26B2E13
The BANK ACCT DETAILS.exe file in the BANK ACCT DETAILS.rar attachment has a file size of 1,291,264 bytes. The MD5 checksum is the following string: 0x48F623342AA5B67987CCE2E1AA92F243
A variant of the TT COPY.exe file in the TT COPY.rar attachment has a file size of 1,637,376 bytes. The MD5 checksum is the following string: 0x3AF02783FAD3C6CA56F1F862DE2210A0
The Swift.exe file in the Swift.rar attachment has a file size of 556,544 bytes. The MD5 checksum is the following string: 0x018421FBD38A8B7BDAB10E235C56CB61
The following text section is a sample of the email message that is associated with this threat outbreak:
> Subject: Fwd: TT COPY
Message Body:
**Dear Sir,
Here is the attached copy of TT payment made to your account today.
20 SENDER’S REFERENCE **
Or
> Message Body:
**Please find attached payment transfer details for your kind reference and do revert back ASAP.
Hussain
**
Or** **
> Subject: Re: The Payment Have Been Made
Message Body:
**Good Day Sir/Ma,
find attach, is payment slip made as promised by my company against invoice sent. Arrange
to dispatch the materials as soon as possible.
Thank You
**
Or** **
> Message Body:
Dear Sir/Madam
Kindly check the attached scanned copy of the balance Payment Slip Transfer bank deposit made to your Bank Account this
Morning by your Customer today.
Please check for confirmation if the Transfer was made into the right bank account and get back to us urgently.
Please confirm receipt
Regards,
Or
> Subject:** Re: Payment Slip**
Message Body:
Bonjour Monsieur,
Nous sommes très désolé pour le retard dans la réponse,
joint le bordereau de paiement visé
à la semaine dernière P S, Endeavor de revenir à
nous dès confirmé.
Merci
Or
> Subject: Re: tt copy
Message Body:
**Dear Sir/Madam
Kindly check the attached scanned copy of the balance Payment Slip Transfer bank deposit made to your Bank Account this Morning by your Customer today.
Please check for confirmation if the Transfer was made into the right bank account and get back to us urgently.
Please confirm receipt
Regards,
(Payment officer)
**
Or
> Subject: CSIRT-Submissions
Message Body:
Dear Sir/madam
With instruction from your customer,please find attached in this email copy of our payment remittance made to your bank and contact your bank immediately to confirm our payment.
Please remember to proceed with the shipping as agreed earlier.
Thanks for your understanding,
Regards,
Or
> Message Body:
**Dear sir/Madam,
With reference to the above subject and as per the requirements placed by you on us, we have attached herewith the Proforma Invoice dated. 23.11.2013 for purchase made on the 17th of Feb 2014
You are kindly requested to reconfirm bank account details as we arrange for deposition of your payment .
Your urgent attention in this matter will be highly appreciated.
Please confirm by return mail.
Thank you and kind Regards,
Accounts Department
**
Or
> Subject: PROCEED WITH THE SHIPMENT
Message Body:
REGARDS
--
Or
> Subject: **Remittance copy **
Or
> Subject: Payment Receipt for Invoice #102376
Message Body:
**Kindly find the payment receipt attached to this message and confirm if
there has been no error in the account paid into and the amount paid.
Thanks.
**
Or** **
> Subject:** Refer to the attach file**
Message Body:
**The attached payment slip is issued at the request of our customer. The slip is for your reference only. Yours faithfully, Global Payments and Cash Management. **
Or
> Message Body:
Hello Dear
Sorry for the inconvenience,we wrongly made payment to your account instead of our vendor please find attached the swift copy and confirm your account details is correct. We will send you our account details to refund back the money when it hit your account.
Once again sorry for the troubles.
Regards
Or
> Subject: Re:Your TT Copy Payment Slip.
Message Body:
**Dear Sir/Madam
Enclosed plz find the copy of TT against INV # 0307/2014
(Dated: 27-05-2014).
Thanks
Kind Regard
Farrukh Nawaz Khan
Accounts Manager
**
**Or **
> Subject:Re: Account transaction
Message Body:
**Hello,
Please find attached account statement pertaining the wire transfer.Kindly
check with your bank and keep me posted for confirmation.
Kind regards,
Anna Yang
**
Or
> Subject: Please open the attachment to view your payment slip for confirmation
Message Body:
**Please open the attachment to view your payment slip for confirmation
Telegraphic payment made to you.
Best Regards.
**
Or
> Subject: kindly find telex copy of the payment to your account
Message Body:
**kindly find telex copy of the payment to your account
as we are advised by your customer.
Please confirm from your bank and revert.
HSBC INTERNATIONAL-BANK SETTLEMENT SYSTEM
Presenting Bank: HSBC BANK UAE, 057150000
Cash Letter Collection Type: Telex Transfer
Bundle Collection Type: NEFT Credit
We are sorry for the delay in effecting this payment as a result of international
network breakdown. Please bear with us as we are constantly here to serve
you better.
Thank you and best regards,
**
Or
> Subject: Re: Comprovante deposito 08/09/2014 05:18:12
Message Body:
**Olá
Conforme haviamos conversado no dia 02/09/2014 foi efetuado a transferência para sua conta sobre o estorno da compra, Favor verificar.
Obs: Você pode imprimir o Comprovante Clicando Aqui
Atenciosamente,
VLz Financeiro
**
**Or **
> Subject: Revised proforma invoice URGENT
Message Body:
Dear Sir/Mdam,
Good day
Could you please see the attached revised proforma for your reference.
Kindly amend consignee details as highlighted in red ink and confirm in
other to effect payment on the agreed payment terms.
IF you have any question or correction, please let me know.
Best Regards
MR.M.M.G.Dogan Onal
Or
> Subject: **RE-CORRECT INVOICE AND RECONFIRM BANK ACCOUNT NUMBER FOR URGENT PAYMENT **
Message Body:
**Dear Sir,
Please be informed that we were directed to make payment on behalf of your company from your customer
for the above invoice you sent him,but we notice there in mistake in your bank account Number.kindly reconfirm and
correct the mistakes and send back to us asap for urgent payment.
Kindly acknowledge once received and re-confrim urgently the Bank Account Details to this invoices.
Please let us know, if you have any queries.
Thanks,
Sailesh M. Chandiraman
**
****Or
> Message Body:
**Dear Sir/Madam,
The attached payment advice is issued at the request of our customer. The
advice is for your reference only.
Yours faithfully,
Global Payments and Cash Management
HSBC
**
Or
> Subject: Swift
Message Body:
Good Day. Please refer to the attached payment voucher and TT payment slip for your record as descussed.
Details are as follows:-
Remarks payment made for invoice nos. 2014/0041,0313,0395,0396,0401,0402
> ****
> > > > > > Cisco Security Intelligence Operations analysts examine real-world email traffic data that is collected from over 100,000 contributing organizations worldwide. This data helps provide a range of information about and analysis of global email security threats and trends. Cisco will continue to monitor this threat and automatically adapt systems to protect customers. This report will be updated if there are significant changes or if the risk to end users increases.
Cisco Virus Outbreak Filters protect customers during the critical period between the first exploit of a virus outbreak and the release of vendor antivirus signatures. Email that is managed by Cisco and end users who are protected by Cisco web security appliances will not be impacted by these attacks. Cisco appliances are automatically updated to prevent both spam email and hostile web URLs from being passed to the end user.
Related Links
Cisco Security
Cisco SenderBase Security Network
Call
Send SMS
Add to Skype
You’ll need Skype CreditFree via Skype
Revision History
| * Version | Description | Section | Date |
|---|---|---|---|
| 49 | Cisco Security has detected significant activity on September 25, 2014. | 2014-September-25 19:02 GMT | |
| 48 | Cisco Security has detected significant activity on September 24, 2014. | 2014-September-25 11:54 GMT | |
| 47 | Cisco Security has detected significant activity on September 17, 2014. | 2014-September-19 12:55 GMT | |
| 46 | Cisco Security has detected significant activity on September 10, 2014. | 2014-September-11 13:23 GMT | |
| 45 | Cisco Security has detected significant activity on September 9, 2014. | 2014-September-10 12:53 GMT | |
| 44 | Cisco Security has detected significant activity on September 7, 2014. | 2014-September-08 14:06 GMT | |
| 43 | Cisco Security has detected significant activity on September 3, 2014. | 2014-September-05 10:34 GMT | |
| 42 | Cisco Security has detected significant activity on August 24, 2014. | 2014-August-26 12:32 GMT | |
| 41 | Cisco Security has detected significant activity on August 18 2014. | 2014-August-19 12:36 GMT | |
| 40 | Cisco Security has detected significant activity on August 3, 2014. | 2014-August-05 12:54 GMT | |
| 39 | Cisco Security has detected significant activity on July 26, 2014. | 2014-July-28 12:05 GMT | |
| 38 | Cisco Security has detected significant activity on July 7, 2014. | 2014-July-08 12:56 GMT | |
| 37 | Cisco Security has detected significant activity on June 23, 2014. | 2014-June-25 13:05 GMT | |
| 36 | Cisco Security has detected significant activity on June 22, 2014. | 2014-June-23 14:46 GMT | |
| 35 | Cisco Security has detected significant activity on June 16, 2014. | 2014-June-16 20:37 GMT | |
| 34 | Cisco Security has detected significant activity on June 12, 2014. | 2014-June-13 13:09 GMT | |
| 33 | Cisco Security has detected significant activity on June 10, 2014. | 2014-June-11 12:55 GMT | |
| 32 | Cisco Security has detected significant activity on June 10, 2014. | 2014-June-10 12:41 GMT | |
| 31 | Cisco Security has detected significant activity on June 6, 2014. | 2014-June-09 12:06 GMT | |
| 30 | Cisco Security has detected significant activity on June 5, 2014. | 2014-June-06 12:40 GMT | |
| 29 | Cisco Security has detected significant activity on June 2, 2014. | 2014-June-03 12:06 GMT | |
| 28 | Cisco Security has detected significant activity on May 29, 2014. | 2014-May-30 13:36 GMT | |
| 27 | Cisco Security has detected significant activity on May 27, 2014. | 2014-May-28 12:54 GMT | |
| 26 | Cisco Security has detected significant activity on May 24, 2014. | 2014-May-27 12:11 GMT | |
| 25 | Cisco Security has detected significant activity on May 9, 2014. | 2014-May-12 11:41 GMT | |
| 24 | Cisco Security has detected significant activity on May 5, 2014. | 2014-May-06 12:46 GMT | |
| 23 | Cisco Security has detected significant activity on May 1, 2014. | 2014-May-02 13:17 GMT | |
| 22 | Cisco Security has detected significant activity on April 30, 2014. | 2014-May-01 11:47 GMT | |
| 21 | Cisco Security has detected significant activity on April 28, 2014. | 2014-April-29 13:36 GMT | |
| 20 | Cisco Security has detected significant activity on April 22, 2014. | 2014-April-24 12:26 GMT | |
| 19 | Cisco Security has detected significant activity on April 22, 2014. | 2014-April-23 14:20 GMT | |
| 18 | Cisco Security has detected significant activity on April 21, 2014. | 2014-April-22 13:10 GMT | |
| 17 | Cisco Security has detected significant activity on April 15, 2014. | 2014-April-16 11:23 GMT | |
| 16 | Cisco Security has detected significant activity on April 15, 2014. | 2014-April-15 12:51 GMT | |
| 15 | Cisco Security has detected significant activity on April 2, 2014. | 2014-April-04 13:39 GMT | |
| 14 | Cisco Security has detected significant activity on March 28, 2014. | 2014-March-31 12:57 GMT | |
| 13 | Cisco Security has detected significant activity on March 27, 2014. | 2014-March-28 12:24 GMT | |
| 12 | Cisco Security has detected significant activity on March 25, 2014. | 2014-March-27 12:27 GMT | |
| 11 | Cisco Security has detected significant activity on March 24, 2014. | 2014-March-25 12:23 GMT | |
| 10 | Cisco Security has detected significant activity on March 19, 2014. | 2014-March-20 12:46 GMT | |
| 9 | Cisco Security has detected significant activity on March 13, 2014. | 2014-March-14 12:46 GMT | |
| 8 | Cisco Security has detected significant activity on March 11, 2014. | 2014-March-13 14:21 GMT | |
| 7 | Cisco Security has detected significant activity on March 11, 2014. | 2014-March-12 12:59 GMT | |
| 6 | Cisco Security has detected significant activity on March 8, 2014. | 2014-March-10 13:03 GMT | |
| 5 | Cisco Security has detected significant activity on March 3, 2014. | 2014-March-04 12:46 GMT | |
| 4 | Cisco Security has detected significant activity on February 17, 2014. | 2014-February-18 14:32 GMT | |
| 3 | Cisco Security has detected significant activity on October 21, 2013. | 2013-October-22 14:25 GMT | |
| 2 | Cisco Security has detected significant activity on September 8, 2013. | 2013-September-09 13:34 GMT | |
| 1 | Cisco Security has detected significant activity on June 25, 2013. | 2013-June-25 14:23 GMT | |
| Show Less |
Legal Disclaimer
- THIS DOCUMENT IS PROVIDED ON AN “AS IS” BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE ALERTS AT ANY TIME.
A standalone copy or paraphrase of the text of this document that omits the distribution URL is an uncontrolled copy and may lack important information or contain factual errors. The information in this document is intended for end users of Cisco products