Per 
Special Containment Procedures: SCP-5000 must stay contained within an air-gapped computer terminal in Site 15. This terminal needs to be physically secured with non-electronic locks and is to remain unpowered outside of authorized testing. Site 15 AI THEIA is to monitor all Foundation networks for suspicious activity fitting SCP-5000's electronic pattern. If discovered, MTF Kappa-10 ("Skynet") and MTF Rho-9 ("Technical Support") are to be deployed immediately to isolate and purge all instances of SCP-5000.
Description: SCP-5000 is an advanced self-replicating malware capable of releasing reinforced magnetic containment locks1 connected to the Foundation network. Analysis of the MCL's indicates that their polarity has been reversed through dimensional replacement2, causing a subsequent repulsion to occur. How SCP-5000 exhibits this ability, and the entity which created the program is still under investigation.3
SCP-5000's execution command initiates once it confirms the presence of specific parameters in the affected system. The execution of the code triggers the manifestation of SCP-5000-1 within 5 meters of the terminal.
SCP-5000-1 is an indistinct humanoid figure that can only be observed through digitized media and de-manifests when SCP-5000's running code is terminated. Although all attempts at verbal communication with SCP-5000-1 have been unsuccessful, it has been observed to acknowledge others around it through the use of exaggerated body language.4
SCP-5000 was discovered on 9/15/████ on the Foundation's network. Probes scanning for its digital signature detected that the malware was spread over 74% of the Foundation network. Of the detected instances, only approximately 10% of them had been executed, with 8% activating in high-security level sites. How SCP-5000 gained access into the Foundation network is under investigation. MTF Rho-9 has been tasked with its removal.
Addendum 5000-1
INCIDENT REPORT 5000.1
Incident Report ID #: 5000-A1
Summary: On 07/19/████, Site 119 initiated a 119/B/Coldsilver Lockdown Response Code following containment breaches of six Large Scale Aggressors, four Non-Terminable Threats, and five other extradimensional anomalous threats. O4 approved the detonation of Site 119's nuclear warhead one hour and thirty-four minutes after the Lockdown Response Code was initiated. Site 68 received a backup of files, sent by Director David Bold, 26 minutes after the destruction of Site 119. Included in the backup was one folder of encrypted files and one image taken after the detonation. Following the incident, MTF Epsilon-11 ("Nine-Tailed Fox") was dispatched to establish a perimeter around the affected area.
MTF ε-11 was unable to locate any threats after Site 119's detonation. However, MTF ε-11 reported sightings of 5 unidentified individuals 3 days following Site 119's destruction. MTF ε-11's attempt to apprehend the individuals were unsuccessful5. MTF ε-11 was immediately relieved by MTF Nu-7 ("Hammer Down") and sent to Site 68 for medical treatment and debriefing. 6 weeks after the detonation, MTF Omicron-2 ("Nuclear Nomads") was sent to investigate the remains of Site 119.
MTF o-2 discovered 15 compromised MCLs in the remains of Site 119. This incident is recorded as the first insertion point of SCP-5000 into the Foundation's network infrastructure.
INTERVIEW LOG 5000.1
Interviewed: MTF ε-11 Captain Daniel Druid
Interviewer: Researcher Argost
Foreword: MTF ε-11 arrived at Site-68 and was sent for immediate decontamination. Captain Daniel Druid, platoon leader, was the first to recover and was debriefed by Researcher Argost.
<Begin Log>
Argost: Good afternoon, Captain Druid. I'm going to be debriefing you regarding Site 119. I know you're still recovering, so I'll make this quick.
Druid: Fine by me.
Argost: Anything notable happen during your time there?
Druid: The first two days were quiet. Then on the third, motion sensors picked up a bunch of guys breaching the perimeter from the northwest.
Argost: What happened then?
Druid: I sent Chase, Adams, Rico, and Gonzalez to check it out, and another squad to cover their entrance. By the time they got there, the intruders were gone.
Argost: Any visuals, hallmarks you could see? Or was it faulty equipment?
Druid: Definitely not the tech, there were plenty of footprints and other things that showed a group had been there recently. Roger got a good visual on them, said they carried standard tactical gear for a normal fireteam. Well organized. Even might be the ones who hit one-one-nine.
Argost: But why come back? Were they looking for something?
Druid: Couldn't tell you even if I wanted to, doc. I have a small feeling that they were responsible for this. But of course, I'm not here to assume. I don't know what we saw, so let's leave it at that.
Argost: Understandable. Anything else you can tell me about your experience?
Druid: Nah, nothing that won't already be on the report.
Argost: Alright, thank you for your time, Captain Druid.
<End Log>
Closing Statement: Their mission concluded, MTF returned to Site-01 after completion of their decontamination procedures. It was later concluded that the 5 individuals who were discovered near Site 119 were likely associated with the Chaos Insurgency.
Addendum 5000-2
EXPERIMENT LOG 5000.1
Date: 04/03/████
Experiment Number : 5000-A
Protocol: SCP-5000 runs on a standard computer terminal.
Results: SCP-5000 remained dormant for approximately one hour before replicating. Replication continued as a background task for 30 minutes until SCP-5000's code self-terminated. 20 replicates were later discovered in a hidden file.6 The terminal was powered off to prevent the spread of these replicates.
Experiment Number : 5000-B
Protocol: SCP-5000 runs on a standard computer terminal connected to a MCL.7
Results: SCP-5000-1 manifests within the chamber, and is detected by camera feed of the chamber. Researchers within the chamber cannot observe SCP-5000-1, however, SCP-5000-1 acknowledges their presence by shaking its fists at them, then begins to hover over the MCL.
After 1 minute, SCP-5000-1 de-manifests and the MCL is opened. Results are similar to the MCLs in Site 119. A function was later detected running as background process.
Experiment Number : 5000-C
Protocol: SCP-5000 runs on a standard computer terminal connected to a motorized lock.
Results: SCP-5000 was unable to access the mechanism. It then proceeded to replicate as observed in Experiment 5000-A. Computer terminal was powered off.
Five redundant logs have been removed
Experiment Number: 5000-I
Protocol: SCP-5000 performs standard procedure while cameras record the MCL.
Results: Footage of the lock reveals that the magnet moved a displacement of 3 micrometers approximately 56 nanoseconds before the lock was released. This has been concluded to be a side effect of the magnet being substituted and replaced through several dimensions of space-time.
Addendum 5000-3
On 03/24/████ Site 71 reported a containment breach of 2 LSA's and 1 NTT following an experiment involving SCP-5000 at Site 15. The containment breach was later contained by MTF Rho-9 and resulted in 6 casualties. MTF Rho-9 discovered an activated sequence of SCP-5000 before the incident, which has been included in SCP-5000's documents.
struct group_info init_groups = { .usage = MAGNET_INIT(4) }:
struct group_info *groups_alloc(int dimensiontrans){
group info *group_info;
int nblocks;
int i;
nblock = (magsetpol + NGROUPS_PER_BLOCK - 1) / NGROUPS_PER BLOCK;/* Establish points of contact for the entire quadrants, not just a portion. Keep intentional files within encrypted folders. Make sure we don't forget password. Type it all as one word, look for Access phrases.
nblocks = nblocks ? : 1;
group_info = ketrcont(sizeof(*group_info) + nblocks*sizeof(gid_t *), PSWRD_PHRASE = FALL;
if (!group_info)
return NULL;
This segment has been concluded to control how SCP-5000 executes its dimensional replacement once it detects a viable MCL. Investigations are ongoing as to the other properties that this computer script exhibits, as well as how this instance was initiated at Site 71.
Researcher's Note: On 03/26/████, after receiving reports of unauthorized experimentation, Site Director Norva removed Researcher Argost from any projects relating to SCP-5000. An investigation of Researcher Argosts experimentation revealed that he was in possession of an encrypted file. Foundation webcrawlers are currently decrypting the file, however no information has been gathered. Researcher Jak has become the new lead researcher for SCP-5000 until otherwise specified.
