Back to Virginia Unemployment

Javier Mendoza

Unemployment text message link scam real how to verify identity theft claim with Virginia VEC

So I'm dealing with something that completely blindsided me this week. I work in retail and got laid off about three weeks ago, filed my Virginia VEC unemployment claim right away, started my weekly certifications, everything seemed fine. Then out of nowhere I get a text message with a link claiming to be from VEC asking me to verify my identity. I did NOT click it because every instinct told me it was sketchy, but now I'm paranoid - what if it was actually legit? And what if someone already used my info to file a fraudulent claim under my name before I even filed mine? My CSS portal is showing my claim but there's this weird pending verification flag I can't explain. I've been trying to call Virginia VEC for days and cannot get through to a single human being. I need to know: how do I actually verify whether that text was a scam or real, and how do I report potential identity theft on my unemployment claim? The whole situation has me spiraling because if someone stole my identity and filed before me, I could be on the hook for an overpayment I never even received.

Those mystery text messages from 'VEC' are something a lot of us have run into lately. I had my own identity situation with Virginia VEC a few months ago and the ONLY way I got it sorted was by actually speaking to someone at VEC live on the phone - because the CSS portal just kept showing error flags with no explanation. After burning through two entire days trying to reach anyone by phone, I found a service called Claimyr (claimyr.com) that waits on hold with Virginia VEC for you so you end up on the phone with a live agent - there's even a video showing how it works at https://youtu.be/GK1CFuX4p2k. I was skeptical but I genuinely ended up talking to a VEC agent within a couple hours instead of getting endless busy signals. The agent told me right away whether the text I'd received was part of a legitimate ID.me verification push or a phishing attempt - that's the kind of thing you can ONLY confirm by talking to someone, the portal won't tell you.

0 coins

The ID.me angle is a really important detail here. Virginia VEC does legitimately use ID.me for identity verification, and sometimes they send communications through third-party channels, which is exactly why these things are so hard to distinguish from scams. But the link format matters - legit VEC identity verification links go through id.me domains, not random shortlinks.

0 coins

I appreciate you mentioning that service - two days of busy signals is exactly where I'm at right now. The CSS portal has this verification pending flag and there's nowhere on the site that explains what triggered it or what I'm supposed to do about it. Did the agent you spoke with actually document the identity concern in your claim file, or was it just a verbal conversation?

0 coins

My neighbor dealt with almost the exact same thing last spring - got a sketchy text, panicked, couldn't reach VEC - and the whole thing dragged on for six weeks before her claim got unfrozen. She wishes she'd found a faster way to reach someone at the beginning instead of waiting and hoping the portal would update on its own.

0 coins

The text message thing has gotten really out of control. Here's what I used to think - I figured any official government text would have an official .gov link and be totally safe to click. Turns out that's not how it works at all. Virginia VEC partners with ID.me for identity verification, so legitimate VEC texts actually link to id.me, not a vec.virginia.gov address. Scammers have gotten very good at mimicking that exact format. The dead giveaway for a phishing text is usually a shortened URL (bit.ly type links), a sender number that's just random digits rather than a recognizable short code, and language that creates extreme urgency like 'your benefits will be suspended in 24 hours.' If yours had any of those features, do NOT click it and report it to the Virginia Attorney General's office as well as VEC.

0 coins

Mine had a shortened URL and the 'respond within 48 hours or your claim will be suspended' language - both red flags you just described. I'm now pretty confident it was fraudulent. But my bigger worry is whether someone ELSE already used my info to file - is there a way to check that through the portal without calling?

0 coins

You can try logging into your CSS portal at uidirect.vec.virginia.gov and checking the claim history tab. If there's a claim filed under your SSN before your actual filing date, it'll show up there - but sometimes it doesn't and you still need a human to look at the back end of the system.

0 coins

Reporting to the AG's office is good advice but you should also forward the actual text message to 7726 (spells SPAM on a keypad) - that's the carrier fraud reporting number and it helps get the sending number flagged across networks faster than any government report will.

0 coins

The 7726 tip is genuinely useful, didn't know that one. I always just deleted sketchy texts which obviously does nothing.

0 coins

Identity theft on unemployment claims is way more common than people realize and Virginia VEC actually has a specific process for reporting it. There's a fraud reporting page on the VEC website but honestly for identity theft specifically - as opposed to just reporting someone else committing fraud - you need to do several things simultaneously: file a report at IdentityTheft.gov through the FTC, place a fraud alert with the three major credit bureaus, and notify VEC directly in writing through the portal messaging system. The portal message creates a paper trail that a phone call alone doesn't. Keep screenshots of everything including that original text message if you still have it.

0 coins

The parallel track approach makes sense to me - I hadn't thought about the credit bureau angle but if someone has my SSN they could be doing more than just unemployment fraud. Already placed an initial fraud alert with Equifax this morning and I'll extend it to Experian and TransUnion. The portal message is a good idea too, I'll send one today documenting the timeline.

0 coins

The IdentityTheft.gov report is actually really important for unemployment identity theft specifically because it generates an official FTC Identity Theft Report document that Virginia VEC will accept as part of an identity theft claim dispute - it carries more weight than just your word that something happened.

0 coins

I went through this process last year and the FTC report absolutely made a difference. VEC's fraud team treated my case differently once I had that document number to reference in all my communications with them.

0 coins

My situation was similar and I want to share what actually happened with the 'pending verification' flag specifically because I wasted a lot of time going down wrong paths. I assumed the flag was connected to the suspicious activity I'd reported. It wasn't - it turned out to be a standard ID.me verification step that VEC requires for new claims now, totally routine, but it looks alarming when you're already worried about fraud. The CSS portal doesn't distinguish between 'you need to complete routine identity verification' and 'there's an active fraud investigation on your account' - both show up as a flag with no context. That said, you absolutely still need to report the suspicious text and check whether a duplicate claim exists.

0 coins

That's actually a little bit reassuring, though I'm not ready to assume mine is routine yet given everything. How did you complete the legitimate ID.me verification? Did they send a new link or did you initiate it from within the portal?

0 coins

There's an ID.me verification option within the CSS portal itself - you don't need to wait for a link. Under the account settings or profile section there should be an option to verify identity through ID.me. That way you're initiating it from the official portal rather than clicking any external link.

0 coins

The CSS portal ID.me path is definitely the safest way to handle verification. I ended up having to verify twice because my first attempt had a technical error and VEC flagged my account - took a while to sort out but eventually I got through to a VEC agent using Claimyr which helped me get the duplicate flag cleared way faster than waiting for the portal to update on its own.

0 coins

The duplicate flag situation is exactly why having an actual conversation with an agent matters so much. The portal just shows you a status, it doesn't tell you WHY something is flagged or what you need to do about it specifically.

0 coins

Can we talk about how ABSURD it is that VEC's own communication methods are so indistinguishable from scams that even people who work in tech can't tell them apart? I work in IT and I could not definitively tell you whether a given VEC text is real or fake without additional verification. The government sends communications through third party vendors, uses shortened links, creates urgency - everything the security community tells people to treat as red flags. And then when fraud DOES happen, they act like claimants should have known better. The whole system is designed to fail people.

0 coins

The frustration here is completely valid - there's a real tension between VEC trying to modernize their communication (texting, third party ID verification) and basic cybersecurity hygiene that tells people not to click links in unsolicited texts. The practical advice I give people is: if you get any text from 'VEC', don't click the link in the text, instead go directly to uidirect.vec.virginia.gov yourself and check if there's a corresponding action waiting there.

0 coins

That's genuinely the right answer and I wish VEC would put that exact guidance on their website prominently. 'Never click links in texts claiming to be from us, always log in directly' - four seconds to write that guidance, potentially saves thousands of people from identity theft.

0 coins

My employer's HR department actually sends out a reminder about exactly this kind of thing every few months - go directly to the official website rather than clicking any link in a text or email regardless of how official it looks. Same principle applies here 100%.

0 coins

The identity theft verification process for unemployment claims has a few steps that aren't super obvious. After you file the FTC report, VEC has a dedicated fraud unit (separate from regular claims) and you can specifically request your claim be reviewed by that unit through portal messaging. Reference your FTC Identity Theft Report number in that message. VEC is also required to put a temporary hold on benefit payments while investigating a potential duplicate claim, so if your payments stop, that may actually be VEC doing the right thing rather than something going wrong - though it's still incredibly stressful when you need that income.

0 coins

The payment hold thing is what scares me most honestly - I need those weekly benefits, I got rent coming up. How long do identity theft investigations typically take at VEC? I've seen people say anywhere from two weeks to three months which is an enormous range.

0 coins

The range really is that wide and it depends on how backed up the fraud unit is. Cases where the claimant has an FTC report, has submitted documentation proactively, and has already spoken to a VEC agent tend to move faster than cases where VEC is working from scratch with no prior contact from the legitimate claimant. Front-loading your documentation and communication genuinely helps.

0 coins

The proactive contact point is crucial. VEC's fraud unit apparently works through a queue and claims where the legitimate claimant has already made contact and submitted documentation get prioritized differently than ones where VEC has to track down the real person themselves.

0 coins

I was in an identity theft situation with my Virginia VEC claim about four months ago and the thing that finally moved it forward was getting a live agent to manually flag my account for fraud review while I was on the phone. The portal message alone had sat unanswered for 11 days. I'd tried calling probably 15 times across three days and kept hitting the max hold time cutoff. A friend suggested Claimyr after I complained about it on a group chat - I ended up speaking to a live VEC agent the same evening and they escalated my case to the fraud unit right then. Having that case escalation happen in real time while I was on the phone made a genuinely measurable difference in how fast things moved after that.

0 coins

Eleven days with no response to a portal message on something this serious is wild. And the thing you said about getting the escalation done live during the call rather than just submitting a message - that makes total sense, an agent can actually push something through the system immediately rather than it sitting in a queue waiting to be read.

0 coins

The queue-jumping thing is real - I work adjacent to a government agency (not VEC but similar) and when a claimant calls and an agent actively flags something, it moves differently through the system than a written submission that has to be routed and assigned and reviewed. Phone contact when you need urgent action is not the same as written contact.

0 coins

This matches what I've heard from multiple people who've dealt with VEC fraud cases. The agents apparently do have tools to escalate and flag in real time that the portal messaging system just doesn't replicate.

0 coins

Honestly the fact that something serious like identity theft gets stuck in a portal message queue for almost two weeks is its own kind of problem but I'm not surprised - VEC's written communication response times have always been slow.

0 coins

The original question about whether the text was real is worth addressing directly. Virginia VEC does occasionally send texts but their standard practice is that any identity verification requirement will ALSO appear in your CSS portal as an action item. So if you log into your portal and don't see a corresponding task or notification about identity verification, the text almost certainly didn't come from VEC. The portal and the text notifications are supposed to be synchronized - a text that has no corresponding portal task is a major red flag for a phishing attempt.

0 coins

This is incredibly useful - I went back and checked my portal and there is no identity verification task listed anywhere under my claim actions. That pretty much confirms the text was not legitimate. There IS the pending verification flag but according to another commenter that might just be the routine ID.me step which I can initiate myself from within the portal.

0 coins

The text-to-portal synchronization point is exactly right and it's the clearest test people can apply without having to analyze the link URL or anything technical. No corresponding portal task? Almost certainly not from VEC.

0 coins

Exactly - and this same logic applies to emails that claim to be from VEC. Any legitimate action VEC needs from you will show up in your CSS portal account. The portal is the source of truth, not any text or email.

0 coins

I used to think that just freezing my credit would handle everything if my identity got stolen - took me getting actually defrauded to understand that credit freezes don't prevent unemployment fraud at all. Someone using your SSN and personal info to file unemployment benefits doesn't need a credit check - they're not borrowing money, they're claiming benefits through a government system that verifies identity differently. So the credit freeze step is still worth doing to prevent other damage from the same stolen info, but it doesn't protect your unemployment claim directly.

0 coins

The credit freeze misconception is really common and it's worth spelling out. For unemployment identity theft protection specifically, what actually matters is the fraud alert at the credit bureaus (which flags your file and may trigger more scrutiny on identity verification elsewhere), the FTC report, and direct contact with VEC. Credit freeze is valuable for the broader identity theft situation but isn't the unemployment-specific fix.

0 coins

My mom thought freezing her credit would stop someone from using her identity on a benefits application and found out the hard way that wasn't true. Would've saved her a lot of time if she'd known that upfront.

0 coins

The distinction between 'credit-based' identity theft and 'benefits-based' identity theft is something most people don't know exists until they're dealing with it. They operate through completely different systems and require different response steps.

0 coins

There's a step I haven't seen mentioned yet in this thread - after you've confirmed fraud or even just suspected fraud, you should also check with the IRS. If someone filed an unemployment claim in your name and received benefits, those benefits will be reported to the IRS on a 1099-G form. If VEC sends a 1099-G to whoever committed the fraud but the IRS has that income associated with your SSN, it creates a tax problem for you even if you never received a cent. The IRS has a specific process for fraudulent 1099-G forms and it's worth getting ahead of that early.

0 coins

The 1099-G angle genuinely hadn't occurred to me and now I'm adding it to the list of things to worry about. Though I suppose if VEC confirms no fraudulent claim was filed under my name, the 1099-G issue won't apply - but I'll keep that in mind if it turns out someone did file.

0 coins

Exactly - if investigation shows no fraudulent claim was filed, you're clear on the 1099-G front. But if it turns out someone did file and collect benefits, getting the IRS Identity Protection PIN at irs.gov/ippin is worth doing now regardless so your tax filing next year is protected.

0 coins

The tax angle with fraudulent unemployment benefits is a real problem that caught a lot of people off guard a few years back when benefit fraud was especially widespread. Getting ahead of it now rather than discovering it at tax time is absolutely the right move.

0 coins

Virginia VEC does have a process specifically for requesting a corrected 1099-G if you receive one reflecting benefits you didn't collect. But like everything else with VEC, it goes much faster if you've already established a paper trail of your fraud report and communication with their fraud unit.

0 coins

My experience with the actual VEC fraud unit once I reached them was that they were genuinely knowledgeable and helpful - the problem is exclusively the getting-to-them part. When I finally talked to someone, they walked me through every step, explained exactly what had happened with my claim, and told me precisely what documentation they needed from me. I used Claimyr to get through after days of busy signals and not reaching a live person any other way. The agent I spoke with said they see identity theft claims constantly now and there's a whole protocol for it.

0 coins

That tracks with what others here have said - the people at VEC who handle fraud cases seem to know what they're doing, the bottleneck is just reaching them. At this point I've tried calling at different times of day including right at opening and I've gotten either a busy signal or a 'high call volume, try again later' message.

0 coins

The VEC phones being functionally unreachable during certain periods is a consistent problem that predates the recent fraud wave. Add an increase in fraud-related calls to baseline high volume and it makes sense that getting through is nearly impossible without some kind of strategy.

0 coins

The opening-time strategy sometimes works but honestly even calling at 8:01am when VEC opens I've sat on hold for over 90 minutes before getting disconnected without reaching anyone. It's genuinely a broken system for people with time-sensitive claim issues.

0 coins

The thing about verifying whether a specific text message is real is that Virginia VEC's customer service line is actually the fastest and most reliable way to confirm it - more reliable than parsing the URL, more reliable than the portal (which sometimes lags), and definitely more reliable than anything you'd read on a forum including this one. The challenge is getting someone on the phone, which is a whole separate problem from the question itself.

0 coins

You're right that talking to an actual VEC agent is the most authoritative answer I could get - but I'm now on day four of trying and I'm not sure I want to wait day five just to find out what I could probably infer from the evidence already available (shortened URL, urgency language, no corresponding portal task). Still, for the identity theft piece I really do need to reach someone.

0 coins

The inference from available evidence is probably accurate for the scam question - but for the 'has someone filed a fraudulent claim under my SSN' question, you genuinely do need a human at VEC because the CSS portal only shows claims that are associated with your login, and a fraudulent claim filed with your SSN but different login credentials might not appear there.

0 coins

That's a critical point I hadn't thought through - a fraudulent filer wouldn't use your existing CSS account, they'd create a new one with your SSN. So the CSS portal history check another commenter suggested might not catch it. This strengthens the case for getting a live VEC agent involved rather than relying on portal self-service.

0 coins

I had an identity theft flag on my account that turned out to be a false positive - someone with a very similar name and partial SSN match had triggered some kind of fraud filter and my account got caught up in it. VEC had no way to untangle it without manually reviewing my account history. The process was straightforward once an agent was involved but the initial communication from VEC was just a flag in my portal with no explanation, which had me convinced I was the victim of serious fraud for about two weeks before I got it sorted out.

0 coins

A false positive is actually an outcome I'd be very relieved by - I've been catastrophizing about worst-case scenarios all week. Though I'd still want to confirm it's a false positive rather than assuming, especially given the suspicious text on top of it.

0 coins

Definitely get confirmation either way - the peace of mind of an agent actually looking at your account and telling you 'your claim is clean, here's what the flag actually is' is worth the effort of reaching someone.

0 coins

False positives on fraud flags are more common than people realize. VEC runs automated filters and sometimes legitimate claims get flagged for things like filing from an IP address associated with a VPN, or having an address that was previously used in a fraud case. Getting a human to review and clear it is the only resolution path.

0 coins

Went through the whole identity theft reporting process with VEC about eight months ago. The sequence that worked for me: FTC report first (IdentityTheft.gov), fraud alert at all three credit bureaus, then portal message to VEC referencing the FTC report number, then phone call to actually speak to someone and confirm the message was received and get case escalation. The portal message without the follow-up call sat there. The call without the prior written record also felt less substantive. Doing both together is what actually moved my case.

0 coins

The both-together approach is what I'm planning to do - I've started the FTC report and sent a detailed portal message this morning. Now I need to get the phone call done and from what everyone's saying, that's going to be the hard part.

0 coins

The portal message you've already sent is good because it time-stamps your contact. Even if no one reads it for days, it establishes that you reached out on a specific date. That matters if there's ever a dispute about when VEC was notified.

0 coins

The documentation and timestamping point is really important - in any potential overpayment dispute down the line (which hopefully won't happen but is worth preparing for), being able to show VEC was notified immediately and in writing is valuable. Keep copies of everything including your portal message confirmation.

0 coins

Screenshots of your portal message submission and any reference or confirmation numbers are worth saving somewhere outside the VEC portal itself - if your account ever gets locked or suspended during an investigation, you want that documentation accessible.

0 coins

The original poster's situation highlights something that's genuinely confusing about how Virginia VEC handles identity verification. The system uses multiple channels - texts, emails, portal notifications, sometimes physical mail - and they don't always align or reference each other. So you might get a text that's real but doesn't match anything in your portal because the portal hasn't updated yet, OR you might get a scam text that matches a real portal task coincidentally. The lack of a single clear channel makes this whole area much harder to navigate than it needs to be.

0 coins

The multi-channel problem is real and it's partly a result of VEC trying to modernize their communication methods without fully integrating them. The CSS portal, the text notification system, email, and physical mail are apparently at least partially separate systems that don't always sync in real time.

0 coins

And from a fraud prevention standpoint, the complexity actually helps scammers - the more channels and the less consistent VEC's communication is, the harder it is for claimants to distinguish real from fake. A streamlined, single-channel system would be far easier to protect.

0 coins

My understanding is VEC's IT infrastructure is older than it looks from the outside and some of these systems genuinely aren't well integrated - which is part of why the portal doesn't always reflect what agents see on their end either.

0 coins

The poster already did the right thing by not clicking the link. I want to emphasize that because a lot of people in this situation feel stupid for almost falling for it - the texts that come through are genuinely sophisticated and designed by people who have studied what legitimate VEC communication looks like. Not clicking and coming here to verify is exactly the correct response. Now it's just about working through the reporting and verification steps.

0 coins

I appreciate you saying that - I've been feeling embarrassed even though I didn't actually click it, like I should have immediately known. The fact that experienced IT people apparently can't always tell (someone mentioned this earlier in the thread) makes me feel a bit better about being uncertain.

0 coins

The embarrassment thing is also worth mentioning because it makes people less likely to report these things - they think 'well I didn't fall for it, so never mind.' But reporting the phishing attempt to VEC, the AG's office, and the carrier fraud line actually helps protect other people who might see the same text.

0 coins

The underreporting problem is real - most phishing attempts go unreported because people either fell for it and are embarrassed, or didn't fall for it and thought there was nothing to report. The reports are how the authorities identify fraud campaigns and shut them down.

0 coins

My sister-in-law got one of these texts several months ago and clicked the link before realizing - the page it took her to looked exactly like the ID.me verification page, right down to the logo and color scheme. She entered her driver's license number before her phone's security software flagged the site as fraudulent. The resulting identity theft claim process with VEC took nearly two months to fully resolve even though she did everything right once she realized what happened. Preventive action when you suspect fraud is so much faster than remediation after the fact.

0 coins

Two months is a terrifying timeline when you're depending on benefits to cover bills. I'm going to push hard to get everything documented and reported as fast as possible, and get a VEC agent on the record about my situation, so that if it does turn out there's fraud I'm not starting from zero.

0 coins

The fastest resolution cases I've heard about are ones where the legitimate claimant got to VEC quickly, had their FTC report already filed, and had documentation of when they first noticed the suspicious activity. Time from suspicion to first contact with VEC seems to correlate with resolution time.

0 coins

There's something worth knowing about how VEC's fraud team handles incoming identity theft reports. They apparently have a triage system where cases get sorted by urgency - active benefit payments being made to a fraudulent account get highest priority because there's ongoing financial loss, potential fraud with no confirmed payments made yet gets lower priority. If VEC's system shows no benefits have been paid to anyone under your SSN since your legitimate claim began, your case may move more slowly even though it feels urgent to you personally.

0 coins

That priority logic makes sense even if it's frustrating from my end. If no payments have gone out fraudulently, there's less immediate financial loss to stop. But I still need to know whether a fraudulent claim exists because if there IS one, any delay potentially means more fraudulent payments going out.

0 coins

Exactly, and making that argument - 'a potential fraudulent claim may be accumulating liability' - in your portal message and to any agent you reach is worth doing. Framing it as an active risk rather than a historical concern may affect how it's prioritized.

0 coins

The framing advice is genuinely useful. VEC fraud investigators deal with a lot of cases and how you characterize yours in initial contact does seem to affect how urgently it gets reviewed, based on what I've heard from people who've been through it.

0 coins

In my case I specifically said 'benefits may currently be accruing on a fraudulent claim' in my initial portal message and I think that language helped. It signals that delay has a cost, not just that you want an answer for peace of mind.

0 coins

To summarize what this thread has established for anyone who finds it later in a similar situation: if you get a suspicious text claiming to be from VEC, don't click the link. Check your CSS portal for a corresponding action item - if none exists, the text is almost certainly fraudulent. Report the text to 7726, to the Virginia AG's office, and to VEC through the portal messaging system. File an FTC Identity Theft Report at IdentityTheft.gov. Place fraud alerts with all three credit bureaus. Try to reach a live VEC agent by phone to confirm whether a fraudulent claim exists under your SSN. Keep records of every step and every contact.

0 coins

This is exactly what I needed laid out clearly. I've now done most of these steps - FTC report filed, fraud alerts placed, portal message sent. The remaining piece is reaching a VEC agent and I'm going to try again tomorrow morning and see what happens.

0 coins

The portal message confirmation email, if you got one, is also worth saving - it proves you reached out to VEC on a specific date in case that timeline ever matters.

0 coins

The thing about preserving all your documentation outside the VEC portal is worth reinforcing - email confirmations, screenshots with visible timestamps, even photos of your phone screen showing the original suspicious text before you delete it. This documentation becomes your evidence if you end up in a dispute with VEC down the line.

0 coins

Virginia Unemployment AI

Expert Assistant
Secure