Advance fee fraud warning

happygeek 0 Tallied Votes 276 Views Share

It looks ever more likely that 2009 could indeed be the year of the scam.

Symantec owned MessageLabs is warning that cases of advance fee 419 fraud, along with other financial scams, have spiked as we enter 2009. From December 22nd 2008, through into January 2009, the number of scams detected by MessageLabs more than doubled. The numbers show that this kind of fraud has increased from 4.2 percent to 10.2 percent during the period. That compares to just 3.1 percent during the same time last year.

But that is just the start of it, according to MessageLabs which predicts that 419 scams will start switching tactic from the traditional elaborate prose, which can often be highly amusing courtesy of a poor grasp of the English language. Instead, we are told to expect the scammers to switch to a much simpler message which tries to force the user into replying in order to learn about the so-called business opportunity.

"The new year means new opportunities for spammers," said Paul Wood, Senior Analyst, MessageLabs. "As the economic climate continues to be frosty and the inability to secure credit through official channels remains spammers are tempted by the possibility that consumers facing uncertain futures may be more tempted by some of these hard-to-resist offers."

Dani AI

Generated

Building on 's warning about rising advance‑fee scams, the following consolidates practical, long‑term steps for recognising, analysing, and escalating suspected 419/advance‑fee lures. A quick note on thread replies: the short contact post from is a typical pattern (unsolicited contact placed in public threads), and the offhand dismissal from understates the real risk—documenting examples helps investigators and filter tuning.

Common indicators and a safe analysis workflow:

  • Typical red flags: unsolicited promises of large sums, requests for secrecy or upfront payments, oddly amateur grammar combined with professional-looking logos, and reply‑to addresses that do not match the sending domain.
  • Recommended safe steps: do not reply, do not click links or download attachments, and preserve the message as evidence. Extract the full message source / headers (Gmail: “Show original”; Outlook: “View message details”) before forwarding or sharing with analysts. ()

Operational controls for email owners and admins:

  • Adopt layered authentication and filtering: publish and maintain SPF records, enable DKIM signing, and deploy DMARC with incremental policy rollout (monitor → quarantine → reject). Combine authentication with RBLs, content scanning, and attachment sandboxing; monitor aggregate DMARC reports to spot abuse of brand domains. (rfc-editor.org)

Escalation and reporting:

  • Preserve headers and full message copies; forward suspicious mails to the industry clearing house (APWG) and file formal complaints for financial loss or targeted fraud with IC3 and the FTC. Providers also offer in‑client “Report phishing/spam” actions that improve filters when used. For incidents involving money transfer, banks and local law enforcement should be notified immediately. (apwg.org)

Cautions: public reporting portals can be mimicked—use bookmarked or typed official addresses when filing complaints. Keeping a short catalogue of example scams (anonymised headers and the lure text) is useful for pattern detection by ISPs and law enforcement.

dbabes 0 Newbie Poster

hello nice comment.contact me on (doris.weah@yahoo).com for more details.thank you.

Rashakil Fol 978 Super Senior Demiposter Team Colleague

Yawn.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.