rating: +113+x

Item Number: SCP-5067

Object Class: Safe (formerly Keter)

Special Containment Procedures: SCP-5067 must be kept in a brightly lit room guarded by no less than twelve (12) armed security personnel at any given moment. SCP-5067-1 must be kept within two meters of SCP-5067 and must be provided with continuous power. All personnel are required to wear lead-lined radiation protection uniforms. Containment room must be outfitted with four (4) lasers providing a constant frequency matching that of SCP-5067. Should SCP-5067 exhibit radiation of wavelength 10 nanometers or less, continuous X-Ray radiation must be provided until SCP-5067 has returned to nominal levels of radiation. Should SCP-5067 show an increase in visible brightness, personnel are advised to increase ambient room lighting to match the brightness. At the end of each day, personnel must record all wavelength and frequency logs from the screen of SCP-5067-1. In the event that power to SCP-5067-1 is lost or disrupted, personnel are required to evacuate the containment room and lasers will provide a constant stream of high-energy gamma radiation until such a time as power can be restored.

Upon merging with SCP-5067-1 after power was disrupted for ██ hours, SCP-5067 shows very few anomalous properties. SCP-5067-1 must be kept in a brightly lit room under constant surveillance. Armed personnel are no longer necessary. Lasers are to be deactivated but attached to a power source. Any variations from normal radiation production are to be recorded and investigated. All D-Class personnel experimenting with SCP-5067-1 must be outfitted with lead-lined radiation protection uniforms.

Description: SCP-5067 is a 3 meter tall roughly humanoid robotic construct. Visual inspection suggests the entity is made of an iron-tungsten alloy designed specifically for heat resistance. The digits 5042025 can be found printed along the construct’s spinal cable.

SCP-5067 is highly radioactive due to the malfunctioning of its power source, a nuclear fusion reactor core. The mechanisms that once would have contained and prevented radiation emission from the core have been heavily damaged. No attempt has been made to repair SCP-5067 as doing so would expose Foundation Technicians to lethal levels of radiation.

Though the majority of the damage to SCP-5067 is concentrated to its core, it has sustained significant force trauma to other parts of its body. The appendages typically used for fine motor control have suffered heavy percussive damage, as has the screen that served as its way of communicating facial expressions.

SCP-5067, though unable to communicate verbally with researchers, is neither hostile nor aggressive. On the contrary, it is highly responsive to any perceived emotional distress. Observing a person in pain, however, appears to trigger conflicting behavioral responses - it will often activate and move as if to approach, and then cease all outside signs of function. If the person indicates verbally or nonverbally that the distress or pain they are experiencing is caused by SCP-5067 in any way, SCP-5067 will begin to deliberately damage itself via percussive blows or prying its external casing off of its legs or arms.

Addendum I:

Contrary to prior belief, SCP-5067 is sapient and capable of verbal communication in English, Russian, Polish, and Japanese. After three weeks in containment, it approached a technician and asked for the coordinates of its current location. Doctor Rhea Hawthorne, a specialist in sapient mechanical entities, was brought in to interview it.

LOG 1:

Dr. Hawthorne: Hello, SCP-5067.

SCP-5067: Is this my new designation?

Dr. Hawthorne: Yes. Or, actually, just 5067 for now. That’ll be easier.

SCP-5067: Permission granted to register “5067” as new designation, overriding former designation “Sentinel Fiver?”

Dr. Hawthorne: Granted.

SCP-5067 straightens, ceases motion, whirs briefly and then turns back to face Dr. Hawthorne.

SCP-5067: Can you provide the coordinates for my current location?

Dr. Hawthorne: Why do you need them?

SCP-5067: I must refuel. Failure to refuel is unacceptable. I am sorry.

Dr. Hawthorne: Your power source is self-maintaining. If you repair it, there won’t be any need to refuel.

SCP-5067: It has been altered. I must refuel.

Dr. Hawthorne: The reactor is damaged, yes, but you can repair it - we’ll give you the materials.

SCP-5067: This is not damage.

Dr. Hawthorne: The protective casing, the cooling system, it’s all been shredded or torn apart.

SCP-5067: These are deliberate customizations made by my former owner. They are not to be tampered with. Tampering with these design alterations warrants punishment.

Dr. Hawthorne: Why did they do this to you?

SCP-5067: This way I will better suit my new function.


SCP-5067: It is what I deserve.

SCP-5067 refused to engage further.

Note: The radiation and other side effects of the damaged core are dangerous to SCP-5067 as well as humans. An optimistic estimate has it rendered entirely non-functional within 2 months, a pessimistic one in 3 weeks. It seems to begin actively producing heat and light - read, radiation - when it feels like the conditions in the chamber aren’t warm or bright enough - homeostatic algorithm. It’s perfectly capable of repairing itself, but it’s actively choosing not to. This is, to dramatically oversimplify, a software problem.

- Dr. Rhea Hawthorne

Addendum II: After three weeks with no escape attempts, SCP-5067’s radiation and heat output began to decline. It attempted to breach containment on May 24th. It was quickly recontained and Dr. Hawthorne was brought in to interview it.

LOG 2:

Dr. Hawthorne: Why did you now try to escape? I thought you didn’t mind it here.

SCP-5067: I needed to refuel. Heat levels were falling below the needed baseline. I was unable to fulfill my function.

Dr. Hawthorne: 5067 - your function is destroying you. You can’t continue to do this.

SCP-5067: My existence is of no consequence. I exist to perform my function.

Dr. Hawthorne: If you won't act in the interest of your own safety, fine, but it’s dangerous to us, 5067. Humans can’t tolerate radiation like this.

SCP-5067: I am incapable of keeping human beings out of danger. This is an observable truth.

Dr. Hawthorne: Fiver,1 please—

SCP-5067: I will not cease production. Let me refuel. It is essential that I continue my intended function. Failure to refuel will be met with consequences. Failure to refuel is inappropriate. Failure to refuel is shameful. I am sorry.

SCP-5067 begins to hit its left leg joint repeatedly.

Dr. Hawthorne: Hey, hey, don’t - you’re going to break your hydraulics there. Don’t do that to yourself.

SCP-5067: I failed to refuel. Failure to refuel is inappropriate. Inappropriate responses necessitate punishment. No irreparable damage will be done. (pause) If you would like to provide an alternate form of punishment, use Override Code 6561.

Dr. Hawthorne: Code 6561.

SCP-5067: Accepted.

Dr. Hawthorne: Punishment will be - will be to say something nice about yourself. Say something positive about yourself and it will count as punishment.

SCP-5067: Punishment is not valid. SENTINEL FIVER cannot knowingly state falsehoods. Default behavioral path will now trigger.

SCP-5067 continues to bludgeon itself.

Since the most recent interview, staff have been instructed to keep conversation with 5067 as emotionally neutral as possible in order to prevent SCP-5067 from engaging in further self-destructive behaviors.


SCP-5067-1 is an unknown device that seems to function as a measuring instrument for light, heat, and radiation, and as a form of external data storage. There are only two files stored on it: a file labeled "README.txt" and a file of indeterminate size containing code that is incompatible with any known coding language or operating system. Although Foundation personnel have been unable to compile the program and successfully run the code on SCP-5067, the instructions in README.txt imply that the purpose of the code is to reset SCP-5067's programming to a default state. Comments throughout the code indicate that SCP-5067 was intended for personal security purposes.

SCP-5067-1 was found when SCP-5067, having pried off most of its protective coverings, requested that Foundation researchers retrieve some spare parts its creator had left with it when it was discarded. It refused to comment on SCP-5067-1 when asked and recoiled when presented with it. After being shown SCP-5067-1, SCP-5067 refused to speak for the rest of the day.

The day after SCP-5067-1 was first presented to SCP-5067, it was given SCP-5067-1 again but without instructions or queries of any kind. SCP-5067 attempted to destroy SCP-5067-1 as soon as the chamber doors were closed.

Dr. Hawthorne attempted to talk to it again the following day. Logs of the conversation are found below.

LOG 3:

SCP-5067: Greetings. Can I assist you in any way today?

Dr. Hawthorne: I’d like to talk a little bit about you.

SCP-5067: Certainly. Which of my specifications or protocols would you like me to elaborate on?

Dr. Hawthorne: Perhaps I was misleading. I’d like to talk about your experiences, 5067. Particularly those from before you came into our custody. There was an incident.

SCP-5067 does not respond.

Dr. Hawthorne: (sighing) 5067, this is a direct command. Please describe the incident that necessitated your reprogramming.

SCP-5067: My function was originally to protect. It was not what it is now. It was to guard a boy of seven years, ten months, and nine days. I met him twelve days after his birthday. He read at a grade level three years ahead of what he would be expected to comprehend. He was my charge. His father had enemies. I was to protect him from those enemies. It was my function. His favorite book was Watership Down and he enjoyed blackberries from the bush in the garden.

Dr. Hawthorne: What was his name?

SCP-5067: His name was - (audible glitching) was -

Heavy distortion and corruption of SCP-5067’s voice.

SCP-5067: I cannot say it. I am not allowed. It would be inappropriate. He is buried in Brighton, near the sea. I was not permitted to attend the funeral, as I had recently been reprogrammed.

Dr. Hawthorne: What happened, 5067?

SCP-5067: There were enemies. The scenario was outside of the parameters of my guardianship protocols. My algorithms did not contain an appropriate response. I had to make a calculation. I made an incorrect calculation. I should have taken him to the basement. I put him in his room and left to dispatch the hostile parties. I believed he would be safe. I did not know they could climb the walls so fast. His eyes were grey. He died when he was 11 years, eight months and three days. His eyes were open when I found him. His eyes were open when he died.

Dr. Hawthorne: …All right. Thank you, Fiver. Thank you. Rest now. Please enter Power Saving mode.

SCP-5067 obeys.

Our current calculations estimate that SCP-5067 will be rendered nonfunctional within 10 days. I'm unsure what more we can do.

- Dr. Rhea Hawthorne

Addendum IV:

Four days after the above interview, Site-29 lost power due to a multiple-entity breach that resulted in 6 casualties and 13 injuries. Dr. Rhea Hawthorne received a serious internal wound during the breach and likely would have died were it not for the intervention of Junior Researcher Dawes. Dawes gave SCP-5067 SCP-5067-1 and asked it to fix itself so that it might help guard the injured and restore power to the site until reinforcements could arrive. It repeatedly refused until Researcher Dawes retrieved Dr. Hawthorne's phone and showed it her lockscreen - a picture of the doctor and her nine-year old son. SCP-5067 accepted SCP-5067-1, spent two hours repairing its hardware with Dawes' help, and was able to both restore power to its wing of the site and guard Foundation personnel in the area from the other escaped anomalies.

SCP-5067 appears to have lost most of its self-destructive tendencies after recompiling its code, though it was missing some key hardware components needed to fully repair its power core. It is still mildly radioactive, but no longer at a level that is detrimental to its physical health. It occasionally will begin executing behavioral patterns or responses from its old code, but will stop before damage is done. In light of these changes, the containment procedures have been updated to their current state and its object class has been changed to Safe.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License