Member Avatar for MktgRob

Just read on mashable how hackers are using things called botnets to insert code into tweets that carry computer virus from PC to PC. Does anyone know if there are already any protections available for botnets?

  • 2 Contributors
  • 2 Replies
  • 86 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by MktgRob

Dani AI

Generated

As raised and noted, attackers have experimented with using public social feeds as a command channel. Defenses that actually reduce risk fall into three practical groups: platform controls, endpoint protections, and safe client configuration.

Platform controls (what the social network should do)

  • Rate-limit and detect automated accounts and unusual posting patterns to make large-scale command channels noisy and easy to spot.
  • Block or remove accounts used for distribution quickly and revoke malicious API keys.
  • Strip or sandbox active content in feeds so a tweet cannot auto-execute code on a client.

Endpoint protections (what a PC or network should do)

  • Keep the OS, browser, and social clients updated. Many attacks exploit old browser or plugin bugs.
  • Use endpoint anti-malware with web and behavior-based detection, not just signature matching.
  • Enable click-to-play for plugins and script blockers in browsers so embedded content cannot run silently.
  • Route corporate or home traffic through a DNS/web filter or proxy that blocks known malicious domains and expands shortened URLs before the browser opens them.

Client and configuration steps (what users and admins can do today)

  • Remove or audit third-party app access to accounts regularly; revoke apps that are unused or request broad permissions.
  • Configure social clients (including TweetDeck-style apps) to avoid auto-opening links or attachments. Disable preview auto-downloads if available.
  • Use separate profiles or containers for social browsing to isolate cookies and scripts from sensitive sessions.
  • Apply least-privilege to accounts: avoid running admin accounts for everyday use; do not allow social clients to install system-level helpers.

Detection and incident response pointers

  • Monitor unusual outbound connections from endpoints (to many different IPs or to low-reputation domains) — this can reveal botnet callbacks.
  • Keep forensic logs for web requests and process launches; if a social client is implicated, revoke API keys, rotate credentials, and reimage compromised hosts.
  • Work with ISPs or CERTs to report and sinkhole persistent C2 infrastructure.

Cautions

  • URL shorteners and rich previews make malicious links look harmless; always expand and inspect links and the destination domain before trusting them.
  • Social networks change features often; a security setting available today may be removed or altered later—re-check settings periodically.

This approach treats the problem holistically: stop malicious accounts and commands on the platform, harden endpoints so content cannot execute, and change client settings and user practices to reduce the chance of successful exploitation.

Recommended Answers

All 2 Replies

Member Avatar for MktgRob

I know dont about protection against the botnet but I betcha Symantec will develop a software against these botnets. Here is more: http://asert.arbornetworks.com/2009/08/twitter-based-botnet-command-channel/

Thanks for the additional links. I wonder if the firewall companies will develop something to protect PCs where people are using apps like TweetDeck?

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.