|
Title: Why Apple sent you a 2FA text with ‘@apple.com #123456’ at the end Post by: HCK on February 01, 2022, 04:05:11 pm Why Apple sent you a 2FA text with ‘@apple.com #123456’ at the end
<div id="link_wrapped_content"> <body><section class="wp-block-bigbite-multi-title"><div class="container"></div></section><p>If you have logged in recently with your Apple ID and requested an SMS-based second-factor verification code (https://www.macworld.com/article/233903/how-to-bypass-apples-multi-device-two-factor-system-with-messages-auto-fill.html) instead of using the trusted device method, you might have noticed Apple made a change to the text you receive.</p> <p>Previously, Apple sent a message like this:</p> <blockquote class="wp-block-quote"><p>Your Apple ID Code is 123456. Don’t share it with anyone.</p> <p>Starting around November 2021, the codes appear in this format:</p> <blockquote class="wp-block-quote"><p>Your Apple ID Code is: 123456. Don’t share it with anyone. @apple.com #123456 %apple.com</p> <div class="extendedBlock-wrapper block-coreImage center"><div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" src="https://b2c-contenthub.com/wp-content/uploads/2022/01/mac911-combo-apple-sms-code-bordered.png" alt="" class="wp-image-607011" srcset="https://b2c-contenthub.com/wp-content/uploads/2022/01/mac911-combo-apple-sms-code-bordered.png?quality=50&strip=all 778w, https://b2c-contenthub.com/wp-content/uploads/2022/01/mac911-combo-apple-sms-code-bordered.png?resize=300%2C104&quality=50&strip=all 300w, https://b2c-contenthub.com/wp-content/uploads/2022/01/mac911-combo-apple-sms-code-bordered.png?resize=768%2C267&quality=50&strip=all 768w" width="778" height="270" sizes="(max-width: 778px) 100vw, 778px" /><figcaption>Apple has migrated from a plain SMS verification code (top) to one that provides some additional phishing protection (bottom).</figcaption></figure></div></div> <p>Why the change? Apple <a href="https://go.redirectingat.com/?id=111346X1569486&url=https://developer.apple.com/news/?id=z0i801mg&xcust=1-1-606996-1-0-0&sref=https://www.macworld.com/feed" rel="nofollow">proposed in August 2020[/url] that it would support <a href="https://go.redirectingat.com/?id=111346X1569486&url=https://github.com/WICG/sms-one-time-codes&xcust=1-1-606996-1-0-0&sref=https://www.macworld.com/feed" rel="nofollow">“domain-bound codes” for logins[/url]. This kind of code requires sites to make a slight addition to the text messages used for verification codes. The incoming message has to provide a destination domain and some other data. Apple said that this change would improve the integrity of its operating systems offering to autofill the code via a suggestion in the QuickType bar in iOS and iPadOS and a drop-down value in macOS Safari and other macOS apps that take advantage of this feature.</p> <p>Apple proposed this change as a way to deter phishing that tries to intercept and redirect verification codes. In most phishing attacks, the victim gets directed to a fake site that asks them to enter their credentials. The site takes those credentials and silently relays them to login at the legitimate site.</p> <p>But some attackers are wise to two-factor authentication. If the site sends a code via SMS as the default method, the user being phished receives a text message with the code. The phisher then prompts for that code.</p> <p>iOS, iPadOS, and macOS offer to fill in the code most recently arrived via SMS to the Messages app in any properly formatted field—including a phishing site’s verification-code field. That makes it too easy on the scammers.</p> <p>However, if the text message is scoped as Apple suggested, operating systems starting with iOS 15, iPadOS 15, and macOS 11 Big Sur will only offer to autofill on sites that match the domain name. The security isn’t perfect, but it’s a simple update to beef up defensive actions.</p> <p>The format generally looks like this:</p> <ul><li>A standard human-readable message, including the code, followed by a new line.</li><li>The scoped domain as <code>@domain.tld</code>.</li><li>The code repeated again as <code>#123456</code>.</li><li>If the site uses an embedded HTML element, called an iframe, the source of the iframe is listed after %, such as <code>%ecommerce.example</code>. (The original spec specifies @; Apple appears to be using % for its texts.)</li></ul><p>As a user, there’s nothing you need to do. The SMS codes continue to autofill as expected for valid sites.</p> <p>However, you can exercise increased vigilance: when you receive a code in this format as a text message and your app or browser doesn’t offer to autofill it, you could be subject to a phishing trap. Investigate the domain or app carefully before proceeding.</p> <p>This Mac 911 article is in response to a question submitted by Macworld reader Kevin.</p> <h2 id="ask-mac-911">Ask Mac 911</h2> <p>We’ve compiled a list of the questions we get asked most frequently, along with answers and links to columns: read our super FAQ (http://www.macworld.com/article/3077986/os-x/your-top-questions-to-mac-911-and-some-answers.html) to see if your question is covered. If not, we’re always looking for new problems to solve! Email yours to mac911@macworld.com (http://mailto:mac911@macworld.com), including screen captures as appropriate and whether you want your full name used. Not every question will be answered, we don’t reply to email, and we cannot provide direct troubleshooting advice.</p> </body></div> Source: Why Apple sent you a 2FA text with ‘@apple.com #123456’ at the end (https://www.macworld.com/article/606996/apple-verification-code.html) |