Kody Maxson | Breaking Cybersecurity News | The Hacker News

The hacker group Anonymous claims that Maxson is the man who drove Amanda Todd to her death last week, but the Canada native says it wasn't him and that he was a friend to the teen. Alleged Amanda Todd blackmailer Kody Maxson outed a second pedophile blackmailer, known as Viper. Maxson appeared in court Monday for unrelated charges of sexual assault and sexual interference of a person under 16. Anonymous traced him to the online handle Kody1206, an active user on teen chat hub Blogtv where Todd was coerced into exposing herself and various forums dedicated to trading jailbait or sexualized images of teens. Maxson said he got some sketchy information about the blackmailer, who he says was 26, lived in New York and goes by an alias of Viper. The man said he passed this information to the RCMP and NYPD, but he couldn't remember whom he spoke with. He said he only knew Amanda in " a sense ," but denied he was one of her cyber-bullies. Here's a video statement fro

Hacker group Anonymous may have tracked down the sex-obsessed cyberbully who drove a 15-year-old girl to kill herself last week. Today Anonymous posted a video on YouTube naming a 32-year-old man from British Columbia, as the person responsible for the October 10th suicide of 15-year-old Amanda Todd. Anonymous has started #OpRIP to hunt down those who bullied Todd. " This is the pedophile that social engineered Amanda Todd into supplying him nude pictures ," Anonymous said in a Pastebin post before identifying a 30-year-old man living in New Westminster, B.C. Todd committed suicide after years of online abuse by a man who blackmailed her, posted her topless photo online and sent it to her peers. In Todd's video, on handwritten note cards, she detailed the story of a man she said threatened to send photos of her breasts to friends and relatives unless she put on a sexual show for him. She apparently refused and he later made good on that promise, police tol

Identities now transcend human boundaries. Within each line of code and every API call lies a non-human identity. These entities act as programmatic access keys, enabling authentication and facilitating interactions among systems and services, which are essential for every API call, database query, or storage account access. As we depend on multi-factor authentication and passwords to safeguard human identities, a pressing question arises: How do we guarantee the security and integrity of these non-human counterparts? How do we authenticate, authorize, and regulate access for entities devoid of life but crucial for the functioning of critical systems? Let's break it down. The challenge Imagine a cloud-native application as a bustling metropolis of tiny neighborhoods known as microservices, all neatly packed into containers. These microservices function akin to diligent worker bees, each diligently performing its designated task, be it processing data, verifying credentials, or