Shell phishing email with subject Re: Shell Gas Station Knows Rewards! Get your Rewards Here!

For the record, this is a Shell phishing email attempt that is recently going around, with subject "Re: Shell Gas Station Knows Rewards! Get your Rewards Here!"

What to do?  Report them, goto bottom of page. 

From : Shell Gas Station Rewards <noreply@proofserve.com> Subject : Re: Shell Gas Station Knows Rewards! Get your Rewards Here!                         links to

PHISHING LINKs;

1. http://fanroom.shop/?xxxxx....

How to tell this is a Phishing email ?

1. Check email address in full, if it's not from originating company then it's phishing.
2. Hover over all links in email, if it's not from the  company's website then forget it.
3. The best way is to 

How to examine Email Message Source ?

Now lets look at message source

1. Outlook.com->Actions->View Message Source. 
2. Gmail.com->More (down arrow to top right)->Show original.

Check for suspicious links, anything that does not originate from apple.com.

Report Phishing Email (not as Spam)

1. Outlook.com->Junk (at Top)->Phishing Scam
2. Gmail.com->More (down-arrow to top right)->Report Phishing 

Report Phishing

If you have received this email take it further at 

1. https://www.google.com/safebrowsing/report_phish/

Report phishing at Microsoft and subsequently government agencies

1. http://www.microsoft.com/security/online-privacy/phishing-faq.aspx
2. Report Phishing Sites | CISA
3. Home - Canada's Anti-Spam Legislation (fightspam.gc.ca)

C# Parse Linux stat command timestamp with timezone

Here's a prototype on how to handle datetime formats not supported by the limits of the .NET framework's DateTime and DateTimeOffset format strings. 

This code will parse UNIX/LINUX datetime with timezone, specifically as generated by stat command.

stat .bashrc| grep Modify
Modify: 2014-03-30 23:14:47.658210121 -0500

We normally would expect to parse this format  using custom DateTimeOffset format with a ...ParseExact statement.

"yyyy-MM-dd HH:mm:ss.FFFFFFFFF zzz"

On first blush, we expect this to work. A custom format should handle the input we are trying to parse. Note the 9 Fs in a row.  

But this is not supported in the .NET framework. 

This is because .NET datetime format strings will not support consuming more than 7Fs in a row. 7Fs is the limit in terms of accuracy. I was a little shocked at this. Custom formats should handle any combination and permutation thrown at it, but more importantly this is a canonical Linux timestamp! This should have been part of the test suite guys! 

So, here's a way to parser stat command timestamp, but it will lose a tiny amount of accuracy.

The regex here is used to validate the stat datetimeoffset format and truncate the last 2 digits, losing the picoseconds (10^-9) in resolution.  Satisfactory in my situation.

Note: The lowest datetime resolution measurement is a single tick which represents one hundred nanoseconds or one ten-millionth of a second. There are 10,000 ticks in a millisecond (see TicksPerMillisecond) and 10 million ticks in a second.

Here's the static code in case JIT site expires.

using System;using System.Globalization; using System.Text.RegularExpressions;
					
public class Program
{
	public static void Main()
	{
		//Unix Stat CMD CANNOT BE FORMALIZED USING DATETIME and.or DATETIMEOFFSET FORMATS in .NET
		//                                         FFFFFFFFF  not accepted!
		
		string dateString = "2010-11-29 17:56:22.000000000 -0800"; 
		DateTimeOffset unixstatdt = new DateTimeOffset();  
                //                                                                123456789
		if (DateTimeOffset.TryParseExact(dateString, "yyyy-MM-dd HH:mm:ss.FFFFFFFFF zzz", CultureInfo.InvariantCulture, DateTimeStyles.None, out unixstatdt))
		{
				Console.WriteLine("Worked parsed Unix stat datetime with time zone\n        {0}", unixstatdt.ToString ("o"));
		}
		else
		{
			Console.WriteLine("Failed to parsed Unix stat datetime");
		}
		
		//SOLUTION 
		//WE MUST TRUNCATE THE VALUE, CRUDE BUT IT WORKS down to 7 characters from 9
		//REGEX TO VALIDATE AND CONSUME STAT CMD
		string LinuxStatCMDpattern = @"(\d{4}-\d{2}-\d{2})\s(\d{2}:\d{2}:\d{2}\.)(\d{7})\d{2}\s ([\+-]\d{4})";
                string substitution = @"$1 $2$3 $4";
                //ACCEPTED F's of length 7 max
		//                                   123456789
		string input = @"2021-03-17 08:53:39.540802643 +0100";
        RegexOptions options = RegexOptions.Singleline | RegexOptions.IgnorePatternWhitespace;
        
		Regex regexstatcmd = new Regex(LinuxStatCMDpattern, options);
		
		string result = string.Empty; 
		
		if (regexstatcmd.IsMatch(input)) 
			result = regexstatcmd.Replace(input, substitution);					          
		
		Console.WriteLine("Trimmed "  + result);
                //                                                            1234567
		if (DateTimeOffset.TryParseExact(result, "yyyy-MM-dd HH:mm:ss.FFFFFFF zzz", CultureInfo.InvariantCulture, DateTimeStyles.None, out unixstatdt))
		{
				Console.WriteLine("Pass 2: Worked parsed Unix stat datetime with time zone\n        {0}", unixstatdt.ToString("o"));
		}
		else
		{
			Console.WriteLine("Pass 2: Failed");
		}
		
		
	}
}

See it in action using my Clipboard PowerTool ( https://clipboardplaintextpowertool.blogspot.com/ ) which allows you to copy any of the below dates and translate that to current time zone and readable datetime stamp!!!

Date Time Format	DFT Date Time Now
UTC	2023-04-19T16:25:39Z
ISO-8601	2023-04-19T16:25:39+0000
RFC 2822	Wed, 19 Apr 2023 16:25:39 +0000
RFC 850	Wednesday, 19-Apr-23 16:25:39 UTC
RFC 1036	Wed, 19 Apr 23 16:25:39 +0000
RFC 1123	Wed, 19 Apr 2023 16:25:39 +0000
RFC 822	Wed, 19 Apr 23 16:25:39 +0000
RFC 3339	2023-04-19T16:25:39+00:00
ATOM	2023-04-19T16:25:39+00:00
COOKIE	Wednesday, 19-Apr-2023 16:25:39 UTC
RSS	Wed, 19 Apr 2023 16:25:39 +0000
W3C	2023-04-19T16:25:39+00:00
UNIX STAT COMMAND TIMESTAMP	2023-04-19 16:25:39.658210121 +0000
YYYY-DD-MM HH:MM:SS	2023-19-04 16:25:39
YYYY-DD-MM HH:MM:SS am/pm	2023-19-04 04:25:39 PM
DD-MM-YYYY HH:MM:SS	19-04-2023 16:25:39
MM-DD-YYYY HH:MM:SS	04-19-2023 16:25:39

The easy simple way to check if an image has a transparent background

Here's a tip for novices if you want to make absolutely sure your images have a transparent background. Using tools like GIMP can sometimes leave your wondering if your properly set the transparency correctly. 

1. Google to the rescue. Head on over to Google Images. Click 'Search by Image' 'camera' looking icon.
   
   
   
   
   
   
2. Upload your image.
   
   
   
   
   
   
3. If the checkerboard pattern appears in the background, then you have a transparent background. The red arrow points to the checkerboard background.
   
   
   
   
   
   

FAILS 

If your background is black, and you see no chess board pattern, then you have not produced a transparent background. This is a default background color in many image editing programs. 

If your background is white, and you see no chess board pattern, then you have not produced a transparent background. This is a default background color in many image editing programs.