Tuesday, March 19, 2019

You've Been Hacked!!??


Hacked??!!

At some point (if it hasn't happened already) you are going to be the target of some sort of online scam.  Many of these play on the lack of knowledge of the user and fears of the unknown (i.e., computer security).

From a novice's point of view, these can be terribly alarming.  What I have noticed is that the vast majority of these can be deduced with some logic and absolutely zero (or very little) computer prowess.  

I am assuming most people have heard of the scams that a Nigerian prince has left you millions, so let's step away from that one and more to one that is much more intimidating for the uninitiated...

Before we get into deducing the likelihood of an actual threat by logically observing the email, let's see how we can quickly find out information about this email.

In the case of our email scam here, it was sent to the user from their own email address.  How can this be?  They must have your email password??!!  No...not necessarily.  This can be done by spoofing an email address.  That's where you make it appear that the email is sent from an email address which it is not.

Finding the Email's Origin

In order to see where it came from you will need to look at the email header (see the documentation for your email client).  When looking at the email header, keep in mind that the "Received" sections are the most reliable parts of the header.  These form a path from the originating source to your mail server.


The "Received" lines should be read from bottom to the top.  The first "Received" line will be your own mail server while the last will be where the email originated.  That being the case, let's look at the email header in question (to the left)...

Not only do we instantly have some red flags raised because the email is coming from a Chinese server (sorry China!) but we can quickly deduce that they did not send the email from the victim's account, rather it was sent from a different mail server (i.e., in China).  Had they sent it from the victim's actual account, the mail server would be theirs (matching the mail server in the top-most "Received" section).

From here you can use whois tools to determine the source of the IP's and DNS.  You can determine who they belong to and even potentially let them know that their services are being used for nefarious activities.

The Logic of the Scam (or Lack Thereof)

The image to the right is an actual example from an attempt to extort money through fear and playing on a lack of knowledge.  Let's step through it and see if we can deduce the problems herein...

Poor Spelling & Grammar

Note the spelling and grammar issues scattered throughout the email.  This is a textbook trademark of an email scam.

Generalizations

Note that the scammer uses a generic term...that he "cracked your email and digital device".  This is done because you could use a phone, tablet, computer...who knows.  This way he can entice whoever reads.

Blackmail

In this particular threat, the scammer claims to have intimate knowledge of the victim's web usage...specifically they claim the victim visits porn sites.  Now, this is also an easy thing to do with statistics.  It is said that 70% of men and 30% of women go to porn sites according to Patty Lee of the Daily News in 2010.  Other more recent articles place both those numbers much higher.

What that means is that the scammer can make this presumption and hit at least half the people (more if he/she targets emails with male names).

This is a "Fear, Uncertainty, and Doubt" (i.e. F.U.D.) approach.  It uses fear to entice you to comply with their wishes without fully considering the threat.

Techie Jargon 

The scammer then moves in for the kill, using what might sound (to a layman) to be a very convincing technical approach.


This scammer says they gained access to remote your computer and use your camera and see what is on your monitor.  They claim to have gathered all of the victim's data (which would be tons of wasted internet traffic for most people).

They claim to have gathered all of their "passcodes" that were entered on websites.  They claim that changing your data is ineffective because their app refreshes every 5 minutes.

They have "compiled a backup of your device"...
Ok, let me get this straight...you have a backup of my device and ALL of my "passcodes"?  But now you're asking me to send you money...??  

This is the logical flaw here as well.  If they truly had that information, couldn't they merely log into your Google, Apple, and whatever else accounts...likely your bank account.

He also claims to have a "pixel" in the email that will let him know you read the "letter".  Um...no.

Then he moves to something along the lines of "Facebook Pixel" and how this is something used by the authorities to track people.  A quick Google search will reveal this is for tracking Facebook ads.

Bottom Line

Don't be driven by fear...examine the threat with a rational and logical mind.  That alone should help discredit 90% of the scams.  Look at email headers to find where they came from.  You can use tools to look up IP addresses or look up DNS names to see who the originator is.  Many times these can be servers or computers that are compromised.

Potentially you are receiving the email because one of your contacts fell for it and ended up unknowingly providing them what they wanted through their ignorance and fear.

Ask.  Everyone has a "computer guy"...ask someone you trust who is knowledgeable.  Not sure yet??  Ok, feel free to ask me.

Thank you for reading...if this was a help, please pass it on (like and share!).

Joseph Foster

joseph@fostercode.com

(844) 779-3274 ext. 700
www.fostercode.com

Monday, January 2, 2017

Technical Debt Can Kill Your Startup


Introduction

Most startups are already creating their demise and don't even know it yet!  This article will take a look at "technical debt" and provide you some insight from a software engineer with over 20 years of experience working for fortune 500 companies.

What is "Technical Debt"?

Technical debt, in essence, is applied when you put some technical solution off until later and apply a temporary solution in place. The debt that is to be paid is the time and effort it takes to apply the final solution later. You are borrowing tomorrow's exhaustion!
"You are borrowing tomorrow's exhaustion!"

Go On…

Just as there is interest on a loan, there is interest on technical debt…and it grows the longer you wait just the same. It’s the habit of many start-ups and project managers, to allow technical debt without keeping very good track of it.


If it were financial, we’d have something written in a ledger to quantify it. We should spend time, as a general practice, assessing the technical debt we are laying up for ourselves. If you don’t have the time to assess the expense, you are essentially taking a loan with an unknown interest rate and amortization.
"Be aware of technical debt and have a plan to pay it off!"
Don’t misunderstand me, I have collected my share of technical debt. I am not opposed to it, any more than I am to financial loans. Sometimes you need to borrow that time in order to get a task done on time.

What I am really getting at is that it should not be arbitrary or rough guesses. You should be well aware of your debt and have a plan to pay it off. Some of the most horrendous problems I've seen (at Fortune 500 companies) have been directly due to massing technical debt without regard to what that actually means and no plan to pay it back.

The Solution?

Pay your bills. Be aware of what you are actually doing, understand there is an additional cost to performing a task later. The interest I spoke of before is real and
will be applied to your debt. If you are saving 10% by putting it off, you are being counterproductive because your interest will almost certainly be more.
"...everything I put off will cost me later."

I follow a simple rule, everything I put off will cost me later. Be careful not to shake your head too early, most times it’s not directly related to the product. It’s the collateral damage you collect. Changing one product small item will a myriad of known and unknown risks. The more you work in the field, the more you are aware and the better you can account for them…as long as you are looking.

Agile doesn't mean “no planning” neither does it mean to ignore or put off problems. Be careful to collect technical debt as you would loans (i.e. after careful consideration!). Be mindful of your time and you’ll reap the benefits of efficiency and all the perks that go with it.