Documented instance of SCP-8473 (Sensitive information redacted)
Item #: SCP-8473
Object Class: Keter
Special Containment Procedures: Mobile Task Force Gamma-5 (“Red Herrings”) is to maintain a disinformation campaign promoting basic internet safety practices and avoidance of suspicious emails or links. Foundation webcrawlers are to continue saturating inboxes of online users worldwide with phishing, junk, and scam mail to desensitize and normalize such messages, thereby reducing the risk of civilian interaction with SCP-8473 until more reliable containment measures are developed.
Description: SCP-8473 is a phishing email sent from an unregistered, untraceable source. While the message content varies, each instance claims the recipient’s finances, identity, or account access has been compromised and requires immediate verification. An embedded link redirects the recipient to a CAPTCHA-based verification page.
Each email contains a unique URL usable only by its intended recipient. Attempts to access the same link from other devices, accounts, or individuals result in a generic error page or time-out.
The interface initially resembles a routine CAPTCHA prompt, asking the user to verify that they are a human. However, prolonged use progressively begins to diverge from standard verification procedures, instead issuing tasks that reference the subject’s personal history, immediate surroundings, and actions carried out beyond the screen. Later stages become increasingly invasive, coercive, physically dangerous and [REDACTED]. Subjects also begin to display a form of compulsive engagement, often resisting or reacting violently to attempts of intervention.
No subject has been confirmed to complete the process, and the total number of stages is unknown. Individuals believed to have reached the endpoint have either disappeared or found to have never existed.
Addendum 1: Test Logs
In order to test SCP-8473, a small pool of D-Class personnel demonstrating heightened loyalty and obedience to the Foundation was granted provisional, limited internet access in an effort to trigger exposure to SCP-8473. Of the 175 subjects selected, only 27 received an instance of SCP-8473 in their inboxes. These 27 were subsequently used for testing to determine the exact operating parameters of SCP-8473, as well as the existence of a potential endpoint.
Test 001:
D-84456 was instructed to access the link contained within SCP-8473. After doing so, the subject was ordered to close the page and access the link a second time.
Results:
The link associated with SCP-8473 appears to remain functional indefinitely, provided it is accessed by the original recipient. When D-34171 was instructed to replace D-84456 and access the same link, the page instead returned a generic error message.
Test 002:
D-84456 was instructed to access the link contained within SCP-8473. D-34171 was then ordered to replace D-84456 at the terminal and attempt to continue the CAPTCHA process.
Results:
Upon D-34171 taking D-84456’s place, the webpage immediately returned an error message. When D-84456 resumed use of the terminal and refreshed the page, the CAPTCHA process continued as normal.
This suggests SCP-8473 is capable of identifying who is interacting with the webpage and whether the user is the original recipient.
Test 003:
D-84456 was instructed to access the link contained within SCP-8473 and continue progressing through the CAPTCHA process for as long as possible.
Results:
D-84456 remained at the terminal for approximately 127 hours, 46 minutes, and 29 seconds before testing was aborted after SCP-8473 began addressing observing personnel directly through newly generated prompts. Despite repeated orders to abort the test, D-84456 refused to leave the terminal and had to be forcibly sedated by security staff.
This suggests that SCP-8473 possesses some degree of sentience and is aware of individuals observing or monitoring the process. D-84456 was recorded as having completed approximately 7,298 CAPTCHA stages before the test was aborted, with no discernible endpoint in sight.
Test 004:
D-34171 was provided with a computer program designed to complete CAPTCHA prompts by mimicking human operation. Upon accessing the link, the subject was instructed to activate the program.
Results:
Upon activation of the program, the webpage failed to respond to any input. When the program was subsequently deactivated and control was returned to D-34171, the page functioned as normal.
This suggests that SCP-8473 is capable of detecting and rejecting automated interaction methods, and that no non-human or assisted processes can be used to determine a potential endpoint.
Test 005:
D-34171 was instructed to attempt direct verbal communication with the webpage.
Results:
No observable change occurred. D-34171 was subsequently ordered to verify that the terminal microphone and camera were operational; no hardware faults were detected. SCP-8473 appears unwilling or incapable in engaging in direct communication with the user.
Test 006:
D-913374 was placed within an isolated containment chamber and provided a radio, with instructions to deliver routine updates regarding the CAPTCHA process. The subject was also granted access to amphetamines to increase concentration, focus, and wakefulness in an effort to complete SCP-8473 as quickly as possible.
Results:
After 5 hours, D-913374 reported that Stage 172 had begun deviating from standard CAPTCHA prompts, requesting the subject’s place and date of birth. Subsequent stages asked for the names of immediate family members, former addresses, and the layout of the containment chamber.
After 8 hours, D-913374 requested a knife after Stage 324 instructed the subject to make a shallow incision across the palm and present the wound to the camera. Despite the harmful nature of the request, the subject appeared indifferent to the consequences and repeatedly insisted the action was “necessary to continue.”
After 10 hours, radio transmissions briefly cut out for approximately thirty seconds. Upon reconnection, D-913374 stated that nothing unusual had occurred, then added that Stage 511 had requested the names of all personnel currently listening.
After 12 hours, D-913374 demanded that the lights in the containment chamber be turned off, stating that Stage 761 required all sources of illumination in the room to be disabled. Once darkness was achieved, the subject confirmed the process had advanced immediately.
After 14 hours, D-913374 requested that observers remain silent. The subject stated that Stage 913 would fail if “it knows that you are eavesdropping.”
After 19 hours, the subject asked personnel to stop using their designation and instead refer to them by their birth name. No such name was present in Foundation records.
After 21 hours, D-913374 requested access to a photograph of themself taken earlier that day, claiming Stage 1,204 required confirmation that they were “still the same person.”
After 26 hours, radio contact was interrupted by incomprehensible whispering later determined not to match the subject’s voice. When communication resumed, D-913374 refused to discuss Stage 1,587 and asked whether anyone else had heard “the instructions.”
After 34 hours, the subject reported that several prompts were now appearing in the room itself rather than on the monitor, and requested permission to “click the door.”
After 51 hours, D-913374 ceased responding to questions not directly related to SCP-8473. All transmissions consisted of short confirmations, repeated apologies, or requests for additional stimulant doses.
[DATA EXPUNGED]
After 78 hours, D-913374 stopped providing updates entirely. An inspection of the chamber revealed it to be empty, with no signs of D-913374. The terminal remained active, displaying a flashing notification reading: “Verification confirmed.”
Subsequent review discovered no record of D-913374 ever existing or having been in Foundation custody. How such a significant error could have occurred remains unknown.
Following these events, all further testing was suspended pending a future date at which SCP-8473’s properties can be more fully understood.
Addendum 2: Discovery
SCP-8473 first came to Foundation attention through discussions posted to obscure internet forum websites in early 2007, in which multiple users described a phishing email that had appeared unexpectedly in their inboxes. Attempts to identify, contact, or locate the individuals responsible for the earliest reports determined that they were either missing or had no verifiable evidence of ever existing.
One documented instance consisted of a YouTube upload depicting an unidentified individual progressing through the CAPTCHA process. The recording continues for approximately twelve hours, after which the individual states that the current instructions require all recording devices to be disabled, and the video abruptly ends soon after. The uploader and subject have never been identified, and no corroborating records of either party have been located.
It remains unknown how many individuals have been exposed to or disappeared as a result of SCP-8473.