Per 
NOTICE FROM TASK FORCE RECOVERY (TFR)
The following report has been severely damaged following a containment breach of SCP-XXXX dubbed incident MMMM/2. The breach and subsequent data loss is currently subject of investigation by a special task force STF Gamma-136 ("Memetic Therapists") (or just "Task Force Recovery"). Due to the severe loss of data, some information in this document is potentially unrelated or incomplete.
— Dr. Sophie Gronberg, TFR Supervisor
Currently Editing:
| ► Dr Sophie Gronberg (id: sg) Site Administration, Site 50, TFR Supervisor |
| ► Dr. Maria Nisch (id: mn) Senior Researcher, Site 50, TFR |
| ► Dr. Yang Zaoui (id: yz) Senior Researcher, Occult Studies Division, TFR |
Special Containment Procedures
The status of SCP-MMMM is currently unknown. It is not contained by the Foundation, however it is unclear whether it was neutralized during incident MMMM/2 detailed within this document, or not. Currently, all containment procedures focus on the reconstruction of all events that happened before and during incident MMMM/2 and the assessment of SCP-MMMM’s status as well as necessary containment procedures.
A special task force for recovery (TFR) at Site 50 has been founded and tasked with reconstruction of said events. This document has been temporarily classified Level 4/MMMM, while the task force is editing it, so potentially classified information can be attached to the document easily. A final classification will be chosen, when the task force’s work has been finished.
Description
SCP-MMMM is a severe cognito hazard. Previous research into the anomalous behaviour of SCP-MMMM has been documented and stored in the foundation database as two research reports, one exploration log, six interviews, approximately 60 to 80 raw data files and containment procedures. All aforementioned documents that were associated with this SCP have experienced severe data corruption during MMMM/2.
| ► Don't we have anything besides 'severe cognito hazard'? ~mn |
| ►► We'll edit the description when we have conclusive evidence. The restored files suggest some properties, but nothing can be confirmed, yet. ~sg |
Addenda
14/12/2018
After incident MMMM/2 most of the documentation about SCP-MMMM was severely corrupted within Foundation databases. This is attributed to a containment attempt during MMMM/2 that resulted in large parts of the documentation being expunged. Since the documentation was assumed to be affected by an associative conceptual infohazard1, the database entry could not be opened for cleanup as this would expose staff to the infohazardous threat. Instead, potentially infected sectors within mass storage were zeroed out2. Since the Foundation database uses an intentionally contrived algorithm to store data to hinder spread of infohazards within the database, a lot more sectors were affected by the purge than initially intended, to ensure complete erasure of affected information. Technical staff was able to partially restore the following exploration log that resulted in the discovery of SCP-MMMM.
| ► This honestly sounds like a concept that attaches to thought or to other concepts. Over a short time it will have infected or replaced pretty much everything you can think about. ~yz |
| ►► Does OSD have anything on that? ~mn |
| ►►► Lilith honestly sounds like OSD terminology. I will ask if there are projects with that name. ~yz |
17/12/2018
Upon request, the Occult Studies Division provided the following document about project Lilith.
| ► This smells like foul play. If the project was rejected, why is there an exploration log mentioning its usage? ~sg |
| ►► It is possible that a prototype existed before the project proposal went through the application process, because we don't usually hassle with the bureaucracy unless we are sure that our project works. But I have no recollection of this project whatsoever, despite allegedly being project lead. The amnestic treatment during MMMM/2 most definitely was not Class B. ~yz |
| ►►► Even then, why would there be an expedition using a denied project? Don't tell me you test your prototypes in unsanctioned field experiments. ~sg |
| ►►►► Of course not. We may be over-ambitious in our proposals but we aren't dumb. Where would we get an MTF without proper papers anyway? ~yz |
19/12/2018
Data forensics brought up two more partially recovered documents. These are video transcripts of interviews with two members of the MTF assigned to MMMM/1 after their return to Site 50.
| ► So there is a whole security team assigned to this mission and nobody knew what they were doing? ~sg |
| ►► If MC authorized association amnestics, surely they must’ve had the clearance level to do so. So Site Command must have records about this operation. Also, the meds must have come from somewhere. ~mn |
| ►►► I am with Site Command and I can assure you, there is no mission with approved Class E amnestics. There aren’t any records of an exploration matching the description within that time frame at all. ~sg |
| ►►►► I take it from the logs, that I was confused about the identity of MC too. Why does nobody know, who the fuck led this mission? ~mn |
| ►►►►► I'll inquire O5 about that. There was an entire security team with no discernible assignment, no one knows who authorized this mission, the mission clearly used an unsanctioned protoype of God knows what, and not a single soul in this entire facility has any recollection of what happened. Foul play is an understatement at this point. ~sg |
| ►►►►►► So, I sent an e-mail to O5 and asked about the mission details. They also have no idea about any expedition matching the details. ~sg |
28/12/2018
| ► The techs finally finished their report on MMMM/2. I got the e-mail yesterday at around 11 pm. Only two minutes later almost the entire report got automatically redacted by an AI with level 06 credentials. I asked the techs when I got here today, but according to them they received mandatory amnestic treatment earlier in the morning. Logs say, the treatment was also authenticated with level 06 credentials. ~mn |
|
► Okay, so whoever ordered the amnestic treatment for our techs, obviously didn't know them. As always, they forgot to flag several files as related to the incident report. Luckily this meant, that the AI wasn't able to redact those files. So I manually dug them up and retraced the steps of this P-4 figure. After the meeting in the report, they went into one of the unused pool rooms. I checked the access logs, the techs didn't even look into the room. One of the terminals was still running and apparently accessed by P-4. Sadly I wasn't able to recover what they were doing, as the entire terminal history was overridden by several gigabyte of log files, filled to the brim with the same error message, a process on the computer was constantly producing:
Apparently it was this faulty process, that classified the MMMM/2 report and ordered the amnestic treatment. P-4 stayed in the pool room approximately for 30 minutes, then they went into the containment chamber of SCP-GGGG. You can check their documentation for another mostly unredacted excerpt of the MMMM/2 report. Its not beautiful, though. ~sg |
| ►► I think we should inquire O5 again about this. We cannot be expected to ascertain the nature and whereabouts about this anomaly, if we can't even access the only report available to us. ~nm |
| ►►► We should be careful. There was an expedition O5 has allegedly no idea about, utilizing a project from OSD that was denied two years ago and has not seen an update since, and critical information is automatically redacted. I cannot help but smell a cover-up. ~yz |
| ►►►► Why would O5 sanction an STF if they wanted to hidsomething? This P-4 person apparently had O5 authorization, but that doesn't mean that the entire council is in on it. And according to the reports, this anomaly is nothing to joke about, so we need the unredacted report as soon as possible. ~nm |
28/12/2018
