Alameda MOAA
Alameda MOAA Alameda MOAA
Member Login    NewsLetter   Support our Charities    Event Calendar    Search          
Alameda MOAA

Alameda MOAA
Alameda MOAA
 
Site Navigation: Collapse

>  Home Page
>  Chapter Info
  >  Calendar
    >  Upcoming Events
    >  Zoom Meetings
  >  Chapter Officers
    >  2024 Alameda MOAA Boar
    >  California MOAA Chapte
  >  Memberships
    >  MEMBERS ONLY
    >  New Members
    >  National MOAA Membersh
    >  2024 Alameda MOAA Memb
  >  About Us
  >  Newsletter
  >  Taps Reports
    >  Brigadier General Ches
    >  Tulio Acquistapace CAP
  >  Member Stories
    >  CDR Kenneth Levin USN
    >  The Origins of Bataan
    >  Japanese American Sold
    >  Captain Sidney Jordan
  >  Donations
    >  ROTC Scholarships
    >  Honor Flight Bay Area
    >  VA Medical Center Live
  >  Base Pass
  >  General Quarterly Member M
  >  Board Mtg Agendas
  >  Member Mtg Agendas
  >  Board Meeting Minutes
  >  Treasurer Reports
  >  Legislative Updates
    >  Assembly Bill 46 Perso
      >  Letter to Governor New
      >  Letter to Your CA Sena
      >  Letter to Senate Appro
      >  AB46 Letter to Senator
  >  By Laws
  >  MOAAA National Membership
  >  Announcements

>  Chapter Programs
  >  Honor Flight Bay Area
  >  ROTC
    >  Chapter Awards ROTC Ca
    >  Fleet Week Special Eve
  >  Guest Speakers
    >  Dr Joel Parrott DVM Oa
    >  LCDR Grant Hatten USN
    >  Mr John Bennett Retire
    >  Rear Admiral Brian Pen
    >  LT Terryll Daguison
    >  Lieutenant Colonel W A
    >  Major Sanjiv Baxi
    >  CAPT David Foote USN R
  >  VA Medical Center Livermor
  >  Coast Guard Retiree Event
  >  Fleet Week Event USS Potom
  >  CALMOAA Resources
  >  Resources
    >  MOAA Career Financial
    >  CouncilChapter Trainin
    >  Important MOAA Dates
  >  Surviving Spouse Program
    >  What to Do When a Mili
    >  Who is Really Contacti
    >  How Well Do You Know T

>  Local Interest
  >  Local Links
  >  Aid For The Deployees Fami

>  National Interest
  >  MOAA
    >  Legislative Update
    >  TOPS
  >  National Links of Interest
  >  VA Resources
  >  President Bidens Fiscal Ye
  >  Benefits for Veterans with

>  Contacts
  >  Contact List
  >  Email Form

Who is Really Contacting You

Learn how to spot a “phishing” scheme before you are a victim.

P. T. Barnum once said, “There is a Sucker born every minute.”  It’s easy to believe him because he was one of the best purveyors of entertainment in history – a genius of sales and marketing – with a whole lot of shenanigans thrown in for good measure. No doubt he would have plenty to say about modern “phishing” schemes to gain access to your personal information and financial assets.

Your Surviving Spouse Liaison is writing today to discuss how to keep your identity and assets safe. Even I have been fooled a few times by what appeared to be a legitimate business. Fortunately, I had my radar up and caught the scam before any damage could be inflicted. In this article I hope to provide some tools to help you as well!

What is “Phishing”?

Phishing is the fraudulent practice of sending emails, texts, or automated calls purporting to be from a reputable company or entity in order to steal personal information. Scammers are after your password, login, credit card numbers and bank account information. They use an authentic looking – but bogus – email, text or logo to obtain information or direct individuals to a fake website or call center to trick you into sharing sensitive information about yourself.

What are some of the most common Examples of Phishing scams?

  • Tech Support phishing email.
  • Tax refund or that you owe taxes by email or phone call.
  • Suspicious activity notice.
  • Bogus payment confirmation email.
  • Incorrect billing or invoice notice.
  • Account suspension email or phone call.

Data released by Proofpoint in 2022 revealed that 80% of respondents experienced an email phishing attack in 2021, a 46% increase from 2020. Hackers use this Social Engineering Tactics to target victims of all ages. In fact, data shows that almost 20% of recipients click on malicious links in phishing emails and answered bogus phone calls.

How to spot a fraudulent attempt to gain your personal information. Here are some examples.

By far, scammers like to use scare tactics, a false sense of urgency, or hard deadlines to trick you into paying for unnecessary technical support or resolve fake problems for your devices, personal accounts and software.

As an example, fraudsters might pose as Microsoft Support Personel, which was the most spoofed brand in 2021. To convince you that there is an issue, your device glitches are presented in technical terms. (Scammers also regularly impersonate tech support brands such as Best Buy Geek Squad).

How tech support scams work:

  • In most cases, scammers ask you for money to fix nonexistent problems on your device or software. If you allow them to remotely access your computer to “fix" these alleged issues, they can install malware or ransomware.
  • They’ll also ask you to pay a one-time fee or subscribe to a support service.

How to spot them:

  • All communications with big companies like Microsoft start with you. Legitimate companies do not contact you via email about device issues. 
  • Be vigilant about requests for remote access to your computer. 
  • Check the sender’s address to see if it’s from a fake domain (for example, it’s not from microsoft.com). 
  • Do not comply with requests for your financial information. As an example, credit card information to bill you for fake services.

Another common example is impersonating the IRS. You may, for instance, receive a fake IRS email asking you to send money to resolve an outstanding balance or request a copy of your W2 because you have a refund due.

The IRS ALWAYS contacts individuals by mail. They will not call you or request personal information in an email or over the phone.

How IRS scams work:

  • You will receive a message from scammers. Using a phishing link, they lead you to a fake IRS site. 
  • When you enter personal information on the site, such as your Social Security Number or bank account number, it goes straight to the scammer. 
  • Installing malware on your computer is another type of fraud. You'll be asked to open an attachment; and when you do so, malicious software is downloaded to your computer. 

How to spot them:

  • See where the email came from. Fraudsters can use fake IRS names. Hover over their name with your mouse or cursor to see their real email address. It is a hack if it's not from a “.gov” address. 

These are just a few ways Scammers will try to obtain your personal information. Phishing attacks come in all different shapes and sizes. But luckily, there are still some clear warning signs that you’re dealing with a scam email or call.

In Review, be Aert!

Follow these tips to help protect yourself from the dangers of phishing:

  • Learn the warning signs of a phishing attack. Scammers will try to create a sense of urgency in emails and calls to get you to act quickly. They want you to click on malicious links (for example, claiming you owe money or need to “verify” personal information) or give information over the phone. Always slow down and check for signs it’s a scam — such as a generic greeting, typos and weird grammar, suspicious links or requests for sensitive information.
  • Always double check the sender’s email address. Scammers use lookalike or spoofed email addresses to fool you into thinking you’re dealing with someone you’re not. Check their email to make sure it comes from an official domain. If you can’t see the sender’s email, double-click or hover over their name to reveal it. If in doubt on a call, hang up and contact your institution directly.
  • Regularly check your credit report and bank statements. Scammers are almost always after your financial accounts. Check for the warning signs of identity theft — such as strange charges on your bank statement or accounts you don’t recognize.In addition, an identity theft protection service can monitor your credit and account statements for you and alert you to any signs of fraud. 
  • Be suspicious of all links. Never click on links in emails from people you don’t know personally (they could lead to fake websites that steal your personal information or infect your device with malware). You can hover over a link to see where it’s sending you. If you’re at all in doubt, visit the site directly (rather than through the link in the email). This includes documents that are unexpected.

There are over three billion phishing emails sent per day. Chances are, if you haven’t seen one yet, you will eventually. And, while no one can prevent every identity theft or guarantee all transactions - awareness and education is your best defense.

If you have any questions or require additional information please contact me. It would be my pleasure to direct you to appropriate resources.

 

 

A picture containing sphere, circle, ball

Description automatically generated Alameda MOAA

Alameda MOAA

Error Occurred While Processing Request The web site you are accessing has experienced an unexpected error.
Please contact the website administrator.


The following information is meant for the website developer for debugging purposes.
Error Occurred While Processing Request

Error Executing Database Query.

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 4
 
The error occurred in C:/home/alamedamoaa.org/wwwroot/template_subpage3.cfm: line 31
Called from C:/home/alamedamoaa.org/wwwroot/pagesub2.cfm: line 806
Called from C:/home/alamedamoaa.org/wwwroot/pagesub2.cfm: line 1
Called from C:/home/alamedamoaa.org/wwwroot/template_subpage3.cfm: line 31
Called from C:/home/alamedamoaa.org/wwwroot/pagesub2.cfm: line 806
Called from C:/home/alamedamoaa.org/wwwroot/pagesub2.cfm: line 1
29 : 	*
30 : 	FROM pagesub3
31 : 	where pagesub2id = #getpagesub2.pagesub2id#
32 : 	</CFQUERY>
33 : 

SQLSTATE   42000
DATASOURCE   moaa_alm7
VENDORERRORCODE   1064
SQL    SELECT * FROM pagesub3 where pagesub2id =
Resources:

Browser   Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Remote Address   18.118.19.162
Referrer  
Date/Time   13-May-24 08:43 AM
Stack Trace
at cftemplate_subpage32ecfm311968896.runPage(C:/home/alamedamoaa.org/wwwroot/template_subpage3.cfm:31) at cfpagesub22ecfm591336895._factor13(C:/home/alamedamoaa.org/wwwroot/pagesub2.cfm:806) at cfpagesub22ecfm591336895.runPage(C:/home/alamedamoaa.org/wwwroot/pagesub2.cfm:1) at cftemplate_subpage32ecfm311968896.runPage(C:/home/alamedamoaa.org/wwwroot/template_subpage3.cfm:31) at cfpagesub22ecfm591336895._factor13(C:/home/alamedamoaa.org/wwwroot/pagesub2.cfm:806) at cfpagesub22ecfm591336895.runPage(C:/home/alamedamoaa.org/wwwroot/pagesub2.cfm:1)

com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 4
	at jdk.internal.reflect.GeneratedConstructorAccessor195649.newInstance(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
	at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
	at com.mysql.jdbc.Util.getInstance(Util.java:387)
	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:939)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3878)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3814)
	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2478)
	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2625)
	at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2547)
	at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2505)
	at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:840)
	at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:928)
	at coldfusion.server.j2ee.sql.JRunStatement.execute(JRunStatement.java:359)
	at coldfusion.sql.Executive.executeQuery(Executive.java:1567)
	at coldfusion.sql.Executive.executeQuery(Executive.java:1317)
	at coldfusion.sql.Executive.executeQuery(Executive.java:1247)
	at coldfusion.sql.SqlImpl.execute(SqlImpl.java:427)
	at coldfusion.tagext.sql.QueryTag.executeQuery(QueryTag.java:1211)
	at coldfusion.tagext.sql.QueryTag.startQueryExecution(QueryTag.java:841)
	at coldfusion.tagext.sql.QueryTag.doEndTag(QueryTag.java:794)
	at cftemplate_subpage32ecfm311968896.runPage(C:\home\alamedamoaa.org\wwwroot\template_subpage3.cfm:31)
	at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:262)
	at coldfusion.tagext.lang.IncludeTag.handlePageInvoke(IncludeTag.java:735)
	at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:565)
	at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:4329)
	at cfpagesub22ecfm591336895._factor13(C:\home\alamedamoaa.org\wwwroot\pagesub2.cfm:806)
	at cfpagesub22ecfm591336895.runPage(C:\home\alamedamoaa.org\wwwroot\pagesub2.cfm:1)
	at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:262)
	at coldfusion.tagext.lang.IncludeTag.handlePageInvoke(IncludeTag.java:735)
	at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:565)
	at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)
	at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:595)
	at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:43)
	at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40)
	at coldfusion.filter.PathFilter.invoke(PathFilter.java:162)
	at coldfusion.filter.IpFilter.invoke(IpFilter.java:45)
	at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:96)
	at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:78)
	at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
	at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
	at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:60)
	at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
	at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
	at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62)
	at coldfusion.CfmServlet.service(CfmServlet.java:226)
	at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:311)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
	at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:46)
	at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:47)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:377)
	at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:463)
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:889)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.base/java.lang.Thread.run(Thread.java:834)