MSEndpointMgr
mypasswordfoundever verified

Never share your password via email or chat. Use the dedicated Foundever employee portals or trusted company resources for all credential management.

Routinely access the built-in Password Checkup utility within your preferred browser settings (Chrome, Safari, or Firefox) to discover hidden exposures.

This article will dissect the "mypasswordfoundever verified" scam, explain the mechanics of how such messages work, provide a clear, step-by-step guide to verifying your actual security, and, most importantly, arm you with the knowledge to protect yourself in the future.

"We have verified that your password is [Your Actual Password]. We have accessed your device and recorded you doing [embarrassing activity]. Pay us $1,000 in Bitcoin or we release the footage."

Offers expert advice on what steps to take if a breach is officially confirmed.

"Verified" downloads or "viewers" are frequently Trojans designed to steal banking info or log keystrokes.

Below is an article exploring the concepts of password verification, data breaches, and how to stay secure.

Disclaimer: This article is for informational purposes. "Foundever" and "myPasswordFoundEver" are trademarks of their respective owners. Always follow your internal IT security policies.

13 comments

  • Hello,

    We followed your guide to the letter on a 2016 and 2019 server but we keep running into the problem that the SCEP application pool keeps crashing for no real reason. We already ruled out a mistake in the templates or wrong CA certs in the intermediate.
    We can see the Cert requests arrive but IIS dies everytime we see this in the NDES log:

    NDES COnnector:
    Sending request to certificate registration point. NDESPlugin 18-4-2019 17:04:05 3036 (0x0BDC)

    Event viewer just shows us that w3wp.exe has crashed and that the faulty module is ntdll.dll.

    We’ve been banging our heads against this problem for a week now so we hope you have any idea where to look.

    Regards,
    Herman

  • Nick, your stuff is amazing as always! .NET 3.5 appears to be required, so may be worth mentioning somewhere since some installations will need to specify an alternate path for that.

    Using your script, I was failing on “Attempting to install Windows feature: Web-Asp-Net” and it wasn’t until I manually added 3.5–specifying the alternate path to the Server installation media–that I could continue.

  • Does this work for Android for Work or Android Enterprise devices? I can’t find the certificate issued to the end mobile devices even – iOS?

  • Hey Nickolay,

    there are two mistakes in your two pictures showing the configuration of the AAP. In the internal URL field you have to write https instead of http, because of the later binding / requiring of SSL. Your other older posts showing this also with https configured.

    Best regards and nice work!,
    Philipp

    • I’ve wasted way too much time troubleshooting this before I checked the IIS log files and they showed port 80. After changing AAD Proxy to HTTPS everything works.

      Great guide though!

  • It appears that the script is expecting to find only 1 client authentication certificate with the specified subject. Could you modify it to handle cases where there are multiple certificates with the same subject?

  • Hello – Is there a mistake with the steps regarding the client and server certificates? At first you emphasized the points of each type which in turn have different Extended Key Usages. Are you stating to use the same template that contains both types?

  • Awesome step by step guide, many thanks. As per usual the MS TechNet lacks a lot of steps and inside information. Regarding the two certs, can they also be 3rd party and trusted certs (wildcard) ?

Sponsors

Categories

MSEndpointMgr.com use cookies to ensure that we give you the best experience on our website.