Arthur T Knackerbracket has found the following story:
IBM is urging customers to destroy flash drives it shipped to storage system customers because they contain malware.
The company warned in an advisory Tuesday that an unspecified number of USB flash drives shipped with the initialization tool for Storwize systems contain malicious code. IBM instructed customers who received the V3500, V3700 and V5000 Gen 1 systems to destroy the drive to prevent the code from replicating.
"When the initialization tool is launched from the USB flash drive, the tool copies itself to a temporary folder on the hard drive of the desktop or laptop during normal operation," IBM said in its advisory.
The malicious code is part of the Reconyc Trojan malware family, which typically targets computers in Russia and India, according to data from Kaspersky Lab.
IBM said that while the malware is copied onto the victim's device, the malicious code is not executed during initialization.
-- submitted from IRC
(Score: 3, Informative) by Scruffy Beard 2 on Friday May 05 2017, @09:15PM (3 children)
Destroying is more reliable than disabling autorun, apparently.
Non-destructive "repair" steps:
(Score: 2) by kaszz on Friday May 05 2017, @09:42PM (2 children)
Can't use a defective OS manufacturer to do the job. Instead a good tool is Unix though one can suspect VMS etc will be ok too.
So this would likely wipe the shit to oblivion:
dd if=/dev/zero bs=64k of=/dev/[SSD device]
(usually takes hours.. but in most cases wiping out the start of a disc makes most handling software to consider it empty)
Less brutal:
mtools.conf: drive m: file="/dev/[SSD device]"
mdel 'm:*.*'
mount.... /dev/[SSD device] /mount
rm -rf /mount/*
rm -rf /mount/.??*
umount /mount
(Score: 2, Informative) by toph on Saturday May 06 2017, @12:22AM (1 child)
Filling a flash drive with zeros allocates all sectors and may adversely effect future performance. Use a proper erase tool if you can find one. Otherwise, the suggestion:
is good. So do:
and then fdisk / mkfs.vfat or whatever.
(Score: 2) by kaszz on Saturday May 06 2017, @01:17AM
Better to write a 1 MB block because 64 kByte is very tight to be sure that no OS-partition-RAID thing mess it up.
dd if=/dev/zero bs=1024k count=1 of=/dev/[SSD device]
Otherwise you may get the .. "Hey! I found a missing RAID parity disc. I will now restore parity on your volume(s) which results in NOOOOOOO!!%¤=%)=¤" ;-)