Hi. I was having same issue and solved it. Here´s the description on my problem and my solution to it. Hope it helps (I was writing a longer post but hit the wrong keys and lost what I wrote).
The thing is that the bandwith was being consumed by iCloud iPhoto Streaming which was turned on. The machine was uploading all the photos to the cloud. So, steps to know if it is your problem and to solve it.
0. Open iPhoto, click on "Photo Stream" and watch the text up in the right (in the title). Is there something saying "Uploading 230 photos"? Then this could be the issue. Close the iPhoto and follow the steps.
1. Open "Activity Monitor" and go the the "Network" tab. Close all the programs, downloads, dropbox, etc. and check if there is some activity in the "Data sent/sec" section. If there is some data being sent there is obviusloy some program in the background using your bandwith. If this is true then it can be the photo stream agent in charge to upload all the photos to iCloud. If not, then this may not be your problem but you could check this out also.
2. Open a "Terminal" and type: "launchctl list | grep com.apple.photostream-agent" (without the quotes of course). This will show you if the photostream-agent is currently running. If there is a line being printed after the command like: "- 0 com.apple.photostream-agent" then the photostream-agent is stopped, but if you get a line with a number instead a dash like "279 - com.apple.photostream-agent" (see the difference? dash + 0 in one case and a number different than 0 and a dash in the second case) then your photostream-agent is running. If this last is your case try stopping it. There is no problem by doing this since after a reboot the agent will start again. So don´t worry in executing this and being afraid on braking something. After a reboot everything will still be the same as before running this command:
3. Stop the photostream-agent. Run. "launchctl stop com.apple.photostream-agent". Once stopped check out with the "Activity Monitor" if there is some data being sent. If this were your problem you shouldn´t see any data going out now (unless you had this problem and another one like a "Dropbox" sending more data in the background or another service you just didn´t noticed yet).
4. If this solved your problem, just be happy and let other people now about the solution.
5. If this didn´t solve your problem and your are still wathing data being sent in the "Activity Monitor" and you are pretty sure that the agent has been stopped (try that 2nd step command again and see if you get a "0" indicating that it has been stopped) I can point you out some command to check where is your data going to:
a. Try this command in the "Terminal": "netstat -n | grep ESTABLISHED". This will show you the connections opened. Check the second and third column. Second column is the receive queu and the third one the send queue. If you got one line showing a number different than 0 (and if the Activity Monitor shows network activity then some of those lines will be different thatn 0) write down that 5th column numbers down. Numbers are separeted by dots. Write them down (those line which have send/receive queue other than 0).
b. Run "whois <ip_address>" where ip_address are the numbers you wrote down WITHOUT the last dot+number. Example: "whois 73.125.231.172" (where your numbers you wrote were "73.125.231.172.80" (note I removed the ".80" in the whois command). Watch for the company name and domain and see if it says something to you.
c. Run "lsof -i -Pn | grep <ip_address>" to check WHICH program is using your bandwith. Try to close that program manually or with the "Activity Monitor" and check if that solved your problem.
d. Force that program to quit if it doesn´t with the "Activity Monitor" or it just doesn´t appear in the "Activity Monitor": "ps -ef | grep <program_name>" and write down the second column number of the program. Run "kill -9 <pid>" where the pid is the second number you wrote down. Check again and repeat steps until no program is using your bandwith.
I really hope this helps.