Per 
Item #: SCP-6174
Object Class: Safe Euclid
Special Containment Procedures: SCP-6174 is to be carefully placed in a 12x9 wooden container that is vertically placed on the side of a small easel and should be inspected daily for harm, as well as blood seeping from it's base. If not handled carefully, SCP-6174 should have all of its wounds, rips, and holes sewn together immediately. SCP-6174 should be kept in 79° degree heat with 0% humidity.
↓*Click Here To See SCP-6174 as of current form*↓
Description: SCP-6174 is identified as a pain-splitting sheet of paper. A stack of SCP-6174 was found covered in blood next to a toddler in the █████ Orphanage. The top page of SCP-6174 was torn in half almost completely identical to the child found next to it. SCP-6174 is able to share the pain/wounds it receives.
Containment is difficult, if not followed up daily. If SCP-6174 receives damage done by a living subject, SCP-6174 will bleed the blood coming out of the subject's wound. If others approach SCP-6174 while it is bleeding, SCP-6174 will then start to ooze their blood in the exact same area. Though there is no real way of telling where the wound will appear, it is most likely in a most fatal location. If the subject is treated and properly stitched up, SCP-6174 will stop bleeding and return to its original state.
SCP-6174 Test Logs;
Log 1:
D-[ REDACTED ] attempts to write on SCP-6174.
Log 1 Results: Subject accidentally hashes open a wound in SCP-6174 and soon perishes from blood loss.
Log 2:
D-[ REDACTED ] attempts to burn SCP-6174.
Log 2 Results: Both [ REDACTED ] and SCP-6174 are disintegrated. SCP-6174 Sheet is replaced with new sheet.
Log 3:
D-[ REDACTED ] attempts to drench SCP-6174 with water.
Log 3 Results: D-[ REDACTED ] lets out a painful screech and is rendered unconscious due to over-hydration.
End Log.
A single stack of SCP-6174 contains papers with bruises, burn holes, stab wounds, tears, rips, scratches, teeth impressions, and folds. Entering SCP- 6174's containment chamber will indefinitely result in all current harm done to the stack to be done to any object around it. Therefore, tests are currently being paused until a better way of retrieval is presented.
