Nerfd.net – RF News & Info

Attempted Fraud Incident Report

Hamshack.ca Attempted Fraud Incident Report

Incident Details:

  • Date of Incident: June 16, 2024
  • Reported by: Hamshack.ca User
  • Suspected Fraudster: “Keith Keith Simpson” (Email: keithkeithsimpson650@gmail.com)

Summary of Incident:

A user from Hamshack.ca (hereafter referred to as “Hamshack User”) posted an item for sale, specifically a radio, and was contacted by an individual using the email keithkeithsimpson650@gmail.com (hereafter referred to as “KKS”). The interaction between Hamshack User and KKS raised several red flags indicative of a potential fraud attempt.

Email Exchange Summary:

  1. Initial Contact:
    • Date & Time: June 16, 2024, 10:47 PM
    • Hamshack User: Provided asking price of $450 plus shipping, inquired about specific pictures needed.
    • KKS: Responded positively, proposing payment via cashier’s check.
  2. Proposed Payment Method:
    • Date & Time: June 16, 2024, 4:10 PM
    • KKS: Reiterated intent to pay with cashier’s check and requested confirmation from Hamshack User.
    • Hamshack User: Suggested e-transfer as the preferred method of payment and requested KKS’s call sign for verification.
  3. Shipping and Payment Discussions:
    • Date & Time: June 16, 2024, 4:21 PM
    • KKS: Insisted on using a cashier’s check and proposed that a shipper would pick up the item after check clearance.
    • Hamshack User: Agreed to arrange pickup only after the cheque cleared and repeatedly requested KKS’s call sign for verification.
  4. Suspicion of Fraud:
    • Date & Time: June 16, 2024, 4:56 PM
    • KKS: Avoided providing a call sign and insisted on receiving Hamshack User’s full name and address.
    • Hamshack User: Reiterated the need for KKS’s call sign and mentioned not allowing KKS’s shipper to come to his house without verification.

Key Red Flags:

  • Insistence on Cashier’s Check: KKS consistently insisted on using a cashier’s check, a known method frequently used in fraudulent activities due to its perceived legitimacy and the delay in banks fully clearing such checks.
  • Avoidance of Verification: KKS avoided providing a call sign or any form of personal verification, which is essential in transactions within certain communities such as amateur radio enthusiasts.
  • Request for Personal Information: KKS requested Hamshack User’s full name and address without reciprocating with their own verifiable information, suggesting a possible attempt to gather sensitive information for fraudulent purposes.

Conclusion:

The email exchanges between Hamshack User and KKS exhibit several indicators of a potential fraud attempt. The persistent avoidance of verification, insistence on cashier’s checks, and requests for personal information suggest that KKS might be attempting to defraud Hamshack User.

Recommended Actions Summary:

  1. Cease Communication:
    • Immediately stop any further communication with the suspected fraudster. Continuing to engage with the fraudster can provide them with more opportunities to gather personal information or to attempt further scams. It is crucial to recognize the signs of fraud early and to cut off all contact to prevent any potential harm.
  2. Ignore Similar Attempts:
    • Do not respond to any future messages that exhibit similar suspicious behaviors. Common red flags include:
      • Insistence on Cashier’s Checks: Fraudsters often prefer this method due to the time it takes for banks to clear such checks, allowing them to disappear before the check is found to be fraudulent.
      • Requests for Personal Information: Be wary of any requests for your full name, address, or other personal details without proper verification. Legitimate buyers and sellers will usually provide their own verifiable information and will be transparent in their communications.

If you receive messages that raise suspicion, it is best to delete them and not engage. Remember to trust your ‘gut feeling’ and exercise due diligence when buying and selling items on-line. 

73 Don VE7DXE

The post Attempted Fraud Incident Report first appeared on Hamshack.

Exit mobile version