Item #: SCP-XXXX
Object Class: Euclid
Special Containment Procedures: SCP-XXXX is to be contained within a closed loop computer terminal in Site 15. The terminal is to be constantly depowered unless testing is authorised on SCP-XXXX. The terminal is to be secured within a standard containment chamber, with a non-electronic locking mechanism. Site-15 AI THEIA is to monitor all Foundation networks for suspicious activity fitting SCP-XXXX modus operandi. If discovered, MTF Kappa-10 (Skynet) and MTF Rho-9 (Technical Support) are to be deployed immediately in order to isolate and purge all instances of SCP-XXXX.
Description: SCP-XXXX is an advanced computer worm that exploits advanced magnetic locking mechanisms (MLM). Analysis shows that the magnetic polarity of the MLMs have been reversed through dimensional replacement1. How SCP-XXXX possesses this ability, and the entity which created the program remains unknown.
When SCP-XXXX is inserted into a computer terminal, it scans the terminal's directory for files or commands related to magnetic locking mechanisms2. If present, SCP-XXXX is activated. The activation of SCP-XXXX also causes the manifestation of SCP-XXXX-1. SCP-XXXX-1 resembles a normal humanoid, with the exception of being completely black in colour3. SCP-XXXX-1 can only be observed through digitized media and does not manifest after SCP-XXXX stops running. All attempts at verbal communication with SCP-XXXX-1 have been unsuccessful. However, it has been observed to acknowledge others around it through the use of exaggerated body language4.
Discovery: SCP-XXXX has been discovered in 74% of the Foundations network. However, only approximately 10% of these instances have actually been executed, with the majority of them happening in high security level Sites. How SCP-XXXX was able to gain access into the Foundation network remains unknown.
Addendum XXXX-1
INCIDENT REPORT XXXX.1
Incident Report ID #: XXXX-A1
Summary: On 10/09/████, Site-119 reported a massive containment breach of Keter-class SCPs, followed shortly by the detonation of its on-site nuclear warhead. initiated a 119/B/Coldsilver following several containment breaches of six Large Scale Aggressors (LSA's), four Non-Terminable Threats (NTT's), and five other dimensional threats. O4 approved the detonation of Site 119's nuclear warhead three hours after its Lockdown Reponse Code (LRC) was intiated. Site-68 would later receive a backup of files, sent by Director David Bold, moments before the destruction of Site-119. Included in the backup was an audio log, a computer backup containing several encrypted files and an image taken shortly before 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 the four NTT's after Site-119's detonation. However, MTF ε-11 reported sightings of several unidentified individuals, 3 days following its destruction. The MTF attempted unsuccessfully to apprehend the individuals5. MTF ε-11 was immediately relieved by elements of MTF Nu-7 (Hammer Down), and sent to Site-68 for medical treatment and debriefing. 6 weeks after the detonation, PTF Omicron-2 (Nuclear Nomads) was sent to investigate the remains of Site 119.
PTF o-2 discovered several tampered MLMs within the remains of Site 119. Analysis revealed the polarity of MLMs had been reversed, causing the affected containment cells to unlock themsleves and releasing Keter-class SCPs. No other relevant information was discovered.
INTERVIEW LOG XXXX.1
Interviewed: MTF Epsilon-11 Officer Daniel Druid
Interviewer: Researcher Argost
Foreword: MTF ε-11 arrived at Site-68 and was sent for immediate decontamination. Officer Daniel Druid, platoon lead, was the first to recover following decontamination, and was debriefed by Researcher Argost.
<Begin Log>
Argost: Good afternoon, Officer Druid. I'm going to be debriefing you regarding your latest time. i know you're still recovering, so I'll make this quick.
Druid: Okay. Fine by me.
Argost: Anything notable happen during your time there?
Druid: 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 of 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. But yeah, I had a feeling that they were responsible for this. Of course, it's up to command to have the final say. They probably won't care about what a soldier like me has to say.
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, Officer Druid.
<End Log>
Closing Statement: Officer Druid and the rest of MTF Epsilion-11 were later sent back to Site-01 after completing their mission. Researcher Argost has also been promoted to the Lead Researcher of SCP-XXXX.
Addendum XXXX-2
EXPERIMENT LOG XXXX.1
Date: ██/██/████
Experiment Number : XXXX-A
Protocol: SCP-XXXX is to be run on a standard computer terminal.
Results: SCP-XXXX remained dormant for approximately one hour before replicating. Replication continued as a background task until SCP-XXXX shut itself off 30 minutes later. 20 replicates were later discovered in a hidden file by Foundation personnel. The terminal was powered off to prevent these replications from spreading.
Experiment Number : XXXX-BProtocol: SCP-XXXX is to be run on a standard computer terminal connected to a Keter-class magnetic locking mechanism.
Results: SCP-XXXX-1 manifests within the chamber, and is detected via camera feed of the chamber. Researchers within the chamber cannot see SCP-XXXX-1, however, SCP-XXXX-1 acknowledges their presence by shaking his its fists at them, then begins tampering with the magnetic lock.
After 1 minute, SCP-XXXX-1 demanifests. The magnetic lock is opened. Anaylsis shows that the polarity of the magnetic lock has been reversed, similar to the MLMs in Site-119. A series of code was later found to have been running in the background, an excerpt of which can be seen below.
Experiment Number : XXXX-C
Protocol: SCP-XXXX is to run on a standard computer terminal connected to a motorized lock.
Results: SCP-XXXX was unable to access the mechanism. The worm then proceeded to replicate as observed in Experiment XXXX-A. Computer terminal was powered off.
Five redundant logs have been removed
Experiment Number: XXXX-I
Protocol:
Results:
Addendum XXXX-3
Foundation personnel discovered a decrypted segment of the SCP-XXXX file script. It has been determined to be non-anomalous in nature.
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_1 = R0tT1N ;
if (!group_info)
return NULL;
An encrypted folder was pointed to several times throughout script. Foundation webcrawlers have been successful in retrieving the folder.
