swampyyy

Item #: SCP-XXXX

Object Class: Keter

Special Containment Procedures: All forms of social media are to be monitored at all times by Staff for instances of SCP-XXXX events. Staff are assisted by program DEADWATCH which performs a deep-scan of all messages sent over public and certain private wireless servers across the globe.

Upon detection of a suspected SCP-XXXX event, MTF-Tau 12 is to be dispatched to the event's location and use A-Class Amnestics on all witnesses to both the event and any coverage of the event. Personnel are to fabricate an appropriate cover story for the SCP-XXXX event, and edit server archives to match said cover.

In the event that any D-Class personnel fitted with tracking devices are the target of a SCP-XXXX event, on site staff operating said tracking devices are to immediately file a copy of any recorded GPS data to Site-██.

Description: SCP-XXXX is an anomalous event occurring globally. It is defined by the instantaneous disappearance of an individual. Disappearances lack any pattern, occurring at random times and in random locations. Victims display no anomalous behavior before suddenly failing to exist. The event occurs at a rate of roughly 2 people every 3 years. Whether all individuals that are victim to a SCP-XXXX event are from the same source is unknown.

Because of the infrequency and randomness of SCP-XXXX events, attempts at tracking a subject after the occurrence of an event has never been recorded.

Transcript of Recorded Video Fragment — 2006-09-02 US-Eastern

Foreword: First recorded instance of an SCP-XXXX event occurring. Recorded on the security system of "Marty's Lodge" in ██████, Ohio. Subjects 1, 2, and 3 had reportedly been drinking that night, were not familiar with the area, and were waiting for a room at the current establishment in the lobby. Subject 4 is not a member of their group, and had been waiting in the lobby for several minutes before their arrival. Subject 5 was the current desk clerk at the time, and had been working since 20:01:43 that night.

<Begin Log, 22:49:01>

<22:49:01>: Subjects 1 and 2 talk to each other incessantly. Subject 3 lays half-conscious in their chair. Subject 4 produces a phone only to pocket it once more. Subject 5 is out of view.

<22:49:05>: Subjects 1 lights a cigarette in the lobby, prompting Subject 5 to verbally warn her not to smoke in the establishment. Subject 1 angrily gets up and begins to walk towards the exit. Subject 2 follows. Subject 4 stares as they leave.

<22:49:06>: Subjects 2 is suddenly the victim of an SCP-XXXX event. Subject 1 approaches the door. Subject 3 wakes up. Subject 4 stares. An audible reaction is heard from Subject 5.

<22:49:09>: Subjects 1 opens the door and holds it open. Subject 3 distressingly exclaims the name of Subject 2. Subject 5 has moved into the frame of the camera, and stares at Subject 2's last seen spot.

<22:49:12>: Subject 4 produces their phone once more and dials local police. Subject 1 glances around for Subject 2. Subject 3 begins to grow hysterical. Subject 5 approaches where Subject 2 was and turns around.

<End Log, 22:49:08>

Closing Statement: The SCP-XXXX event was detected by DEADWATCH on 2006-09-03, flagged for investigation, and officially recognized by staff within an hour. MTF-Tau 12 was deployed and administered amnestics to all remaining subjects, and any civilian witnesses of the security footage. A cover for the disappearance concerning a supposed kidnapping of Mary Molica was produced and successfully deployed.

Addendum 1216.9: Because of the increased frequency of SCP-XXXX events (3 disappearances in 20██, compared to 1 in 20██), attempts to properly contain SCP-XXXX is increased to priority Medium.

Note: SCP-XXXX is used as general classification for any disappearances that cannot be attributed to disappearances that can be linked to non-anomalous activity, or anomalous activity by other SCP. Classification of a disappearance as a SCP-XXXX event is to be evaluated by Staff director of SCP-XXXX, and should be judged on the implausibility of disappearance following non-anomalous circumstances, and the potential of anomalous activity from active SCP in the area. If a SCP-XXXX event is found to be non-anomalous or caused by another SCP's activity, it should be declassified as a SCP-XXXX event.