fresh_shockwave2

Item #: SCP-XXXX

Object Class: Keter

Special Containment Procedures: SCP-XXXX cannot be effectively contained due to the difficulty of neutralising individual instances and detecting them on a large scale. Containment is limited to preventing breaches.

Due to the continued damage and threat posed by SCP-XXXX, neutralisation should be a priority, as well as denying SCP-XXXX access to important devices as well as device networks as a whole.

Description

SCP-XXXX refers to an anomalous piece of code which has manifested itself in many computers and devices estimated to have control of 0.005% to 0.02% of all network-connected electronic devices in the world.

Once a device is infected with SCP-XXXX, any attempt to shut down the device fails, and if it is disconnected from a power source, it will drain all power in capacitors/emergency storage until the device is completely inoperable.

After a device is fully secured, SCP-XXXX will begin to operate it. In the vast majority of documented cases, this simply results in up to 80% of the devices processing power being used for seemingly random calculations similar to that of cryptocurrency mining, which are then sent across a series of networks to an unknown location. If the device is prevented from accessing the internet, SCP-XXXX will attempt to destroy it.

SCP-XXXX's source code has proven impossible to decipher - reverse-engineering and total neutralisation has so far proven futile.

Several Mobile Task Forces have been specially trained against SCP-XXXX. MTF Rho-9 has mostly succeeded in defending the Foundation's networks against SCP-XXXX. MTF Mu-4 and MTF Kappa-10 have been deployed several times to assist in the retrieval and neutralisation of infected devices.

Notable Breaches:

• 3/2/05: Security guards at a car assembly plant in ████ are found dead. Nature of wounds suggests that robotic arms attacked and killed on-duty guards after infection from SCP-XXX. Over 80% of parts in factory found missing. This is the first time SCP-XXXX was found to have been directly responsible for human deaths. Incident was publically deemed an accident.

• 5/9/07: Several large arm contractors report missing weapon shipments. SCP-XXXX found to have infected management computers and ordered drivers to deposit crates of firearms to a safe drop point. No footprints, DNA samples or other evidence was found at given locations.

• 12/5/17: Mass spreading of a ransomware instance of SCP-XXXX presenting itself as "WannaCry". Breached into several government and civilian devices worldwide. Managed to infect a single █████ at Site-██, but was terminated before any damage was done. Incident was blamed on the rogue state of ████ ████.

+ Site-██ Incident 11/4/██

On 11/14/██, a number of strange patterns were detected on Researcher ██████'s Foundation terminal. Upon further investigation, information on [REDACTED], SCP-079 and SCP-682 had apparently been accessed an unusual amount of times. When interrogated, Researcher ██████ claimed to have not accessed this information. Before questioning could continue, Site-██ experienced a total blackout. Control was regained with minimal casualties and no breaches, but Researcher ██████ could not be located after the incident.

Addendum 24/5/17:
We would have to be fools to not recognise SCP-XXXX's intelligence and hostility towards humans. These attacks are not the endgame - it should be obvious that it is preparing for something. Neutralisation must be performed as soon as possible.
- Dr C