October 31 halloween*
[Alex]Man its been a few months since ive captured scp-567.
[Intercom]Alex please report to briefing room 467.
[Alex]The hell?
*Alex arrives at room 467*
[???]Ah!,Alex ive been expecting you.
[Alex]Am i in trouble?
[???]No we need to have a misson briefing to recontain a scp.
[Alex]What Scp breached?
[???]SCP-6096.
[Alex]and i can see that everyone is here too.
[???]Yes.
[Alex]Alright Doc get in with it.
[???]if ya say soo.
ITEM#:
6096
LEVEL3
CONTAINMENT CLASS:
KETER
DISRUPTION CLASS:
VLAM
RISK CLASS:
WARNING
link to memo
guest
SCP-6096 in containment at Site-19.
Special Containment Procedures: Containment of SCP-6096 is to be handled directly by Mobile Task Force Zeta-29 ("Blood Brothers"). SCP-6096 is to be detained in a standard humanoid containment chamber located at Site-19. On-site personnel are to constantly monitor SCP-6096's chamber via video and audio recording devices. Any changes in behaviour are to be immediately logged.
SCP-6096 is to be released from containment whenever it desires.
During an off-site excursion, SCP-6096 is to be escorted directly to its destination by MTF Zeta-29 using whatever mode of transport is most convenient. A secondary team are to move ahead of this main escort group and preemptively dose the target with a high-grade tranquilizer so as to ensure unconsciousness. Once SCP-6096 has successfully terminated the civilian in question, it is to be invited back into containment.
Description: SCP-6096 is an entity, presumably humanoid in shape, the body of which is perpetually concealed underneath a large cotton sheet.
Due to the presence of this sheet, a full physical description of SCP-6096 is not possible. Superficial analysis of the entity, however, indicates that SCP-6096 is 1.55m tall and weighs approximately 48kg. The sheet covering SCP-6096 is larger than the actual body, and typically trails at least a meter behind it when it is mobile. Personnel have been unable to attempt to remove this sheet in order to obtain a more accurate description.
No living being can consciously take an action which would result in harm coming to SCP-6096. 'An action which would result in harm coming to SCP-6096' is a broad category, and has been observed to consist of acts including:
Attempting to attack SCP-6096.
Attempting to order others to attack SCP-6096.
Attempting to trick others into unknowingly attacking SCP-6096.
Attempting to lay a trap for SCP-6096.
Attempting to order others to lay a trap for SCP-6096.
Attempting to trick others into unknowingly laying a trap for SCP-6096.
Attempting to create a device which would independently and automatically cause harm to SCP-6096.
Attempting to leave SCP-6096's presence when doing so would expose the entity to harm.
Attempting to self-terminate, if said self-termination would result in negative repercussions for SCP-6096.
Attempting to remove SCP-6096's sheet.
SCP-6096 is usually docile, allowing itself to be led into containment so long as said relocation would not result in harm coming to it. At periodic intervals, however, SCP-6096 will become active and independently mobile, persistently moving at walking speed towards a target.
In all observed cases, this target has been a human being selected at random from the population of the planet Earth.
Any individual who observes SCP-6096 during an active period will gain an instant awareness of the identity of the current target, along with their location. Additionally, they will find themselves compelled to aid SCP-6096 in reaching and securing its target.
Evidence suggests that SCP-6096's target alone is exempt from its main anomalous property — they are able to take actions which could cause harm to SCP-6096. To date, however, none have been successful in doing so, usually due to the unwilling efforts of the entourage SCP-6096 inevitably accumulates during its journey to the target.
When SCP-6096 physically reaches the target, it will subsume them underneath its cotton sheet. In cases where the victim is conscious, they can be seen and heard struggling against SCP-6096 underneath the sheet for a period ranging from twenty to fourty minutes, after which they will disappear entirely. The cries of distress emitted by these victims suggest that this process is extremely painful.
Following acquisition of its victim, SCP-6096 will return to a docile state.
Addendum 6096-1 (Initial Containment)
SCP-6096 first came to the attention of the Foundation on 09/12/2018, when police in the town of Dernham, New Mexico were called to the home of the local Mallion family. The parents of the family, Samuel and Amanda Mallion, claimed that SCP-6096 had entered their home and caused their sixteen-year-old son, Desmond Mallion, to vanish.
SCP-6096 was still present at the home when police arrived — and when authorities subsequently found themselves physically unable to remove the sheet covering it, agents embedded in the regional government alerted the Foundation and brought the entity into initial containment.
The household of the Mallion family was equipped with several cameras for home security purposes, and so the arrival of SCP-6096 was also captured on film. The following is a transcribed log of the relevant portion of this footage:
(The Mallion family is sat on the couch in their living room, facing the television. Samuel and Amanda Mallion are actively watching television, while Desmond Mallion is scrolling on his phone. The sound of a car pulling in can be heard — this is believed to be Drake Ellen, a local taxi driver, dropping SCP-6096 off outside the house. Several seconds later, Samuel Mallion nudges his wife and points towards the out-of-shot window.)
Amanda: What?
Samuel: You see that?
Amanda: See what? I don't… oh! (laughs)
Samuel: (laughs) You see?
Amanda: Is that a Halloween thing? We're closer to Christmas, aren't we?
(Pause.)
Amanda: It's coming over. That's… oh, it's… it wants… oh… oh…
(Amanda reaches over and grabs Desmond's arm tightly. He looks up from his phone.)
Desmond: Hm? What's up? I'm doing stuff.
Amanda: Nothing, honey, just — oh — just stay there, okay? Just stay with me. Oh, no, no, no…
(SCP-6096 is barely audible as it gently knocks on the front door.)
Samuel: (audibly distraught) I'll get it.
(Samuel shakily gets up from the couch and moves over to the front door. He opens it and SCP-6096 enters.)
Desmond: (laughs) The hell? Is that Kimmy1? What's she all dressed up for? (attempts to pull arm away) Hey, could you let me go? You're — uh, you're kinda hurting me.
(Amanda whimpers.)
Amanda: That's fine, honey, I'm sorry, honey — it's just, d-don't move and it'll be fine, I only hurt your arm when you try to pull away, that's just —
(As SCP-6096 approaches, Samuel moves ahead of it and grabs Desmond's other arm, holding him down against the couch.)
Amanda: — that's just fine, you just stay still, honey, you just close your eyes, it won't hurt if you just close your eyes, I love you, I love you, okay? Honey?! Okay?!
(Desmond attempts to break free, but is unable. He kicks his legs wildly in the air. His phone slips off the arm of the couch and falls onto the carpet.)
Desmond: What are you — I'm serious, let go of me!
Samuel: (crying) Just stay still, son, just stay still. It won't — it won't hurt for long. It can't hurt for long. Stay strong. Stay strong for me.
Desmond: You're going to break my fucking arm!
(SCP-6096 reaches Desmond and begins to subsume him, feet first, under the cotton sheet. Amanda and Samuel watch, mouths open, as Desmond is fully dragged under the sheet, visibly struggling. It appears that they are attempting to scream, but are unable.)
(Desmond begins to loudly scream, and violent thrashing can be seen under the sheet.)
(This continues for thirty-six minutes.)
(Once Desmond has completely vanished, SCP-6096 returns to a docile state. It wraps itself in the cotton sheet and sits down on the carpet, facing the television.)
(Samuel collapses to the floor and curls up into the fetal position, seemingly in a state of shock. Amanda staggers backwards to the far wall, continuing to face SCP-6096, and calls emergency services on her cell phone.)
(All parties remain in the same positions, save for Samuel's occasional rocking, until police arrive.)
All immediate witnesses were dosed with a Class-A amnestic and a cover story for the disappearance of Desmond Mallion was produced. It is currently unknown how long SCP-6096 was operating prior to this event, if at all.
Addendum 6096-2 (Welcome Notice)
And there you have it. Welcome to Mobile Task Force Zeta-29 — the booze is under the sink.
No need to worry about professionalism down here: the higher-ups couldn't demote me if they wanted to. Apparently, my presence as the head of SCP-6096 containment is beneficial enough to it that me being reassigned would count as harming it. Lucky me.
You're probably wondering how we can be shameless enough to say we have this thing under containment. It comes and goes whenever it feels like it, and if it ever decided it didn't want to come back to its containment cell, we have literally no way of forcing it. And, yeah, you're probably also thinking that calling that room a containment chamber instead of a hotel room is just as shameful.
To that I say: you're absolutely right. There's nothing we can do against SCP-6096. Feel free to take a drink until you're able to accept that. Don't hold back — you're going to become very familiar with that bottle anyway. I know I did, the first time I had to hold the door to a maternity ward open for this thing.
The idea of containing SCP-6096 is a bad joke. We all decided a long time ago that the only way out of this nightmare is liquidation, decommissioning, neutralization, whatever you want to call it. But that's no walk in the park either; I've stood in that chamber for hours, gun pointed at 6096's head, screaming at my finger just to tighten slightly. Didn't work. You can't harm SCP-6096, no matter how much you want to. You can't even try to start a Rube Goldberg kind of thing to eventually harm SCP-6096. It's just a fact of the world — maybe a semiohazard or whatever it's called.
The way I see it, then, there are three main ways out of this nightmare:
Another organization, maybe the GOC, takes a shot at it without realizing what they're dealing with. Maybe they think we're transporting something much more dangerous — maybe they think we're in over our heads with it — and they take it out with a drone or something, blow the thing to hell while we're transporting it. A bomb would kill it easy, I think — it feels weak. This would only work so long as the GOC thinks they're bombing something else entirely. If they knew it was SCP-6096, they'd just be contained too.
An .aic deals with it. I don't know if an artificial intelligence is immune to SCP-6096's effects, but the fact that it won't let me tell one of them about it gives me hope. Maybe one day, one of those computers gets a mission, and maybe that mission — by complete coincidence — happens to lead them over to this file. Then they use their superior intelligence to set things up so 6096 runs into an 'accident' out of the blue.
A target gets lucky. Maybe 6096 goes after a gun nut, and the poor guy gets a lucky shot in before we can hold him down. This almost happened once — but Lopez took the bullet. Poor guy bled out while we were holding the target down for 6096. Maybe it'll happen again, go better.
Maybe, maybe, maybe.
Let's be honest — these scenarios aren't scenarios, they're fantasies. The odds of any of these things happening on their own are tiny. Miniscule. The only thing that can really do 6096 in, far as I can see, is sheer coincidence. In the end, all we can do is wait and hope — hope for one of us to make a genuine mistake that gets the right dominoes falling. But I wouldn't hold your breath.
After all, we're so fucking good at what we do.
Charlie Symanski, Commander of Mobile Task Force Zeta-29 ("Blood Brothers")
Is that clear?
[Everyone in the room lol]Yes Sir.
[???]alright now go to San francisco, Gibson Lane 3447 (this road is made up lol) secure the anomaly FAST before a civilian reports is got it.
[Everyone in the room lol]Yes Sir
[???]Alright GO GO GO and alex is the team leader