Who texted me from 44398?

Expect six digits and a named app in one short line.

A common Hinge-shaped text matches the sample above: the number, then "is your verification code for Hinge."

Use it for phone verification, not account chat.

Firebase Authentication is Google's service for apps that need to prove the person signing in controls the phone number on the screen.

Expect the app name to change when a different app uses Firebase.

44398 is not a Hinge-owned number; Google leases the short code and sends phone verification codes for app builders that use Firebase Authentication.

Expect no link in the 44398 verification text.

The code is the payload, so the text does not need to move you to a browser, a payment page, a dispute page, or a callback queue.

Text HELP to 44398 only to identify the sender service.

The HELP path is for sender identity and support information; it is not a way to approve, deny, or cancel an app login.

Treat a 10-digit follow-up asking for the 44398 digits as the attack.

The first SMS can come from 44398 because the attacker typed your phone number into an app; the next text says "send me the code" or "I need it to cancel," and that is the theft.

Treat any link paired with a 44398 code as a copycat login.

A fake from a normal number can push hinge-secure[.]com or hlnge-login[.]com, using a lowercase L to mimic an I; the Firebase verification text carries no link.

Refuse any claim that the code cancels a login.

Reading the digits completes the login attempt started by the other person; cancellation and security controls live inside the app, not in a stranger's text.

Check an unrequested Hinge code as an account event.

If you have Hinge, someone has put your number into Hinge's phone step; if you do not, your number was used by mistake or as bait for a later request.

Distrust a body that hides the app name.

Firebase verification messages identify the app that asked for phone verification; "Your security code is 123456" from a normal mobile number gives you no app to verify and is shaped for harvesting.

Cut off payment, delivery, job, or dating stories that use the 44398 digits.

A buyer says the code proves you are real, a match says it verifies your profile, or a recruiter says it finishes onboarding; all three move the code out of the app.

Hang up on anyone calling themselves Firebase support after the text.

Firebase is the delivery system behind the SMS, not a consumer agent who phones you to collect the code, spell your name, or "lock the request."

Check that the sender is 44398 before treating it as the Firebase thread.

A normal phone number can write "44398 code" in the body, but that does not make it the leased short code; it is a lookalike message.

Read the app name, then stop for five seconds.

If it matches an app you just opened and a phone-number screen is waiting, continue; if it names Hinge while you are not using Hinge, do not use the code.

Type the digits only into the app screen you started.

Do not paste them into SMS, email, chat, marketplace DMs, video calls, dating app conversations, or a pop-up claiming to be support.

Open the named app from its icon if you did not request the code.

Check account access and security there; change the password where the app has one, add stronger login options where available, and sign out devices you do not recognize.

If you shared the code, recover the named app first.

Open the app, use its account recovery, remove unfamiliar sessions or devices, change the password if it uses one, and tell the app's support what time the 44398 code arrived.

Text HELP to 44398 if you need to identify the sender service.

Use HELP for sender identity only; do not include verification digits, and use https://firebase.google.com/support/ for Firebase sender questions.

Report the person who asked for the code, not the 44398 text alone.

Send the scammer's phone number, handle, screenshots, and the named app to that app's in-app support; the Google/Firebase short code only delivered the verification SMS.