Windows 10: Microsoft Defender - fraud attempt

StuartBetheil · Aug 28, 2020

I received an e-mail looking like it was from Microsoft, indication that I had been billed for a Microsoft service. No money had been taken from my account.

I called the numbers on the e-mail with a ring, no answer on 2 of the three numbers.

The third number got me a help desk connection where the tech wanted to get into my computer to "refund my charge" . I hung up.

I saved a screen shot of the e-mail.

Does Microsoft want the information on the fraud attempt?

Thank you.

Stuart

:)

Brink · Aug 28, 2020

Microsoft AI solution to detect mobile bank fraud in less than 2 secs

The future of mobile banking is clear. People love their mobile devices and banks are making big investments to enhance their apps with digital features and capabilities. As mobile banking grows, so does the one aspect about it that can be wrenching for customers and banks, mobile device fraud.

Problem: To implement near real-time fraud detection

Most mobile fraud occurs through a compromise called a SIM swap attack in which a mobile number is hacked. The phone number is cloned and the criminal receives all the text messages and calls sent to the victim’s mobile device. Then login credentials are obtained through social engineering, phishing, vishing, or an infected downloaded app. With this information, the criminal can impersonate a bank customer, register for mobile access, and immediately start to request fund transfers and withdrawals.

Artificial Intelligence (AI) models have the potential to dramatically improve fraud detection rates and detection times. One approach is described in the Mobile bank fraud solution guide. It’s a behavioral-based AI approach and can be much more responsive to changing fraud patterns than rules-based or other approaches.

The solution: A pipeline that detects fraud in less than two seconds

Latency and response times are critical in a fraud detection solution. The time it takes a bank to react to a fraudulent transaction translates directly to how much financial loss can be prevented. The sooner the detection takes place, the less the financial loss.

To be effective, detection needs to occur in less than two seconds. This means less than two seconds to process an incoming mobile activity, build a behavioral profile, evaluate the transaction for fraud, and determine if an action needs to be taken. The approach described in this solution is based on:

Feature engineering to create customer and account profiles.

Azure Machine Learning to create a fraud classification model.

Azure PaaS services for real-time event processing and end-to-end workflow.

The architecture: Azure Functions, Azure SQL, and Azure Machine Learning

Most steps in the event processing pipeline start with a call to Azure Functions because functions are serverless, easily scaled out, and can be scheduled.

The power of data in this solution comes from mobile messages that are standardized, joined, and aggregated with historical data to create behavior profiles. This is done using the in-memory technologies in Azure SQL.

Training of a fraud classifier is done with Azure Machine Learning Studio (AML Studio) and custom R code to create account level metrics.

Recommended next steps

Read the Mobile bank fraud solution guide to learn details on the architecture of the solution. The guide explains the logic and concepts and gets you to the next stage in implementing a mobile bank fraud detection solution. We hope you find this helpful and we welcome your feedback.
Click to expand...

Source: Two seconds to take a bite out of mobile bank fraud with Artificial Intelligence | Blog | Microsoft Azure

Brink · Aug 28, 2020

Microsoft AI solution to detect mobile bank fraud in less than 2 secs

The future of mobile banking is clear. People love their mobile devices and banks are making big investments to enhance their apps with digital features and capabilities. As mobile banking grows, so does the one aspect about it that can be wrenching for customers and banks, mobile device fraud.

Problem: To implement near real-time fraud detection

Most mobile fraud occurs through a compromise called a SIM swap attack in which a mobile number is hacked. The phone number is cloned and the criminal receives all the text messages and calls sent to the victim’s mobile device. Then login credentials are obtained through social engineering, phishing, vishing, or an infected downloaded app. With this information, the criminal can impersonate a bank customer, register for mobile access, and immediately start to request fund transfers and withdrawals.

Artificial Intelligence (AI) models have the potential to dramatically improve fraud detection rates and detection times. One approach is described in the Mobile bank fraud solution guide. It’s a behavioral-based AI approach and can be much more responsive to changing fraud patterns than rules-based or other approaches.

The solution: A pipeline that detects fraud in less than two seconds

Latency and response times are critical in a fraud detection solution. The time it takes a bank to react to a fraudulent transaction translates directly to how much financial loss can be prevented. The sooner the detection takes place, the less the financial loss.

To be effective, detection needs to occur in less than two seconds. This means less than two seconds to process an incoming mobile activity, build a behavioral profile, evaluate the transaction for fraud, and determine if an action needs to be taken. The approach described in this solution is based on:

Feature engineering to create customer and account profiles.

Azure Machine Learning to create a fraud classification model.

Azure PaaS services for real-time event processing and end-to-end workflow.

The architecture: Azure Functions, Azure SQL, and Azure Machine Learning

Most steps in the event processing pipeline start with a call to Azure Functions because functions are serverless, easily scaled out, and can be scheduled.

The power of data in this solution comes from mobile messages that are standardized, joined, and aggregated with historical data to create behavior profiles. This is done using the in-memory technologies in Azure SQL.

Training of a fraud classifier is done with Azure Machine Learning Studio (AML Studio) and custom R code to create account level metrics.

Recommended next steps

Read the Mobile bank fraud solution guide to learn details on the architecture of the solution. The guide explains the logic and concepts and gets you to the next stage in implementing a mobile bank fraud detection solution. We hope you find this helpful and we welcome your feedback.
Click to expand...

Source: Two seconds to take a bite out of mobile bank fraud with Artificial Intelligence | Blog | Microsoft Azure

Santosh_Rai · Aug 28, 2020

defender scans

Hi Ian,

Thanks for posting your query on Microsoft Community.

This issue might occur if you have set any task scheduler for Windows Defender.

I suggest you to delete the task for Windows defender and check if it helps.

Follow the below steps:

Search and open Schedule tasks.

In the left-hand menu, open the Task Scheduler Library, then select
Microsoft >Windows >Windows Defender.

Double-click Windows Defender Scheduled Scan.

Select the Triggers panel, then select Delete.

Hope it helps, reply to us with the status of your issue. We will be happy to assist you.

Windows 10: Microsoft Defender - fraud attempt

Microsoft Defender - fraud attempt

Microsoft Defender - fraud attempt

Microsoft Defender - fraud attempt

Microsoft Defender - fraud attempt - Similar Threads - Microsoft Defender fraud

Microsoft Fraud

Microsoft Fraud

Microsoft Fraud

Microsoft fraud

Microsoft fraud

Fraud with Microsoft

Fraud with Microsoft

Fraud with Microsoft

SPAM, Phishing and Attempted Fraud