Dodge Demon Smokes California Police
Read the full story on The Auto Wire
California Highway Patrol chased a Dodge Demon on the 91 Freeway in Downtown Los Angeles on the night of March 3, but couldn't keep up with the muscle car. Reportedly, the vehicle was stolen and that's why police were in pursuit.Footage taken by Key News Network shows the chase briefly. The gray Mopar seems to black out during the shot, turning its lights off in an effort to make it hard for cops to spot it. Sometimes that move works, but usually only when an area is poorly lit and the car is dark.
The chase left the freeway and went onto surface streets in the downtown area of Los Angeles. With parking garages and other structures to hide in, many suspects running from police in the area like to disappear there.
Police told Key News Network they believe this person is a repeat offender, having run from police several times before. They might just think it's fun to smoke cops or they like to street race and then have to run away – we obviously don't know.
We also can't tell in the brief shot if the back of the Mopar muscle car has a license plate and if it's obscured from view. If the plate is visible, plate readers can alert police to the vehicle's presence, which would then trigger a pursuit.
Most police cruisers would be hard pressed to keep up with a Dodge Demon. With oodles of power and a drivetrain that's built specifically for straight line speed, they are in essence a drag racer that's street legal. Police cars obviously are in a whole different class. In fact, they struggle to keep up with Hellcats, and a Demon is at a higher level of performance.
Image via Key News Network/YouTube
Join our Newsletter, subscribe to our YouTube page, and follow us on Facebook.
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Yahoo
2 hours ago
- Yahoo
People Are Sharing "The Incident" That Made Them Leave Their Partner And Never Look Back, And I Totally Get It
Recently Reddit user u/kaissi1 asked "What did your partner do that made you leave them instantly?" After reading people's stories, I can totally see why they left. Here's what they had to say: 1."He got upset that he and his kids weren't in my will…I was a single mother, and we'd been dating for three months." —ElectricalImplement1 2."He fed my hamster to his friend's snake. Yep, I came home to find my one-year-old hamster gone. I freaked out, and then I found a video of it on his Facebook page." —None 3."I wanted to send myself a copy of a pic he had taken, so he gave me his phone to find it. Previous to this moment, I knew he had a foot fetish, and I found a few covert pics of my own feet. I didn't actually care that much until I found sneaky pics of MY MOTHER'S FEET. Relationship over." —GreenEyedHawk 4."They hooked up with my dad." —stevolaz17 5."She was very drunk and found the car keys I hid from her. I told her I wouldn't let her leave drunk and that I would sleep on the couch if needed (We lived together for over a year at this point). She got in the car, parked in our garage, and I stood right behind it, pleading with her not to drive. She threw it in reverse and would have run me over if I didn't jump up on the trunk and then roll out of the way. That was that. Don't need that in my life." —noleksum12 6."They almost cost me my job by showing up there and causing a scene because they were jealous of my boss. It was mortifying and the last straw." —None 7."It was 7 a.m. on NYE. We were in the airport to fly out and go party. He was still drunk from the night before, stomping behind me like a big baby, hollering at me, 'You know I hate morning flights! Why the hell would you book such an early flight?' And the kiss of death when he hissed, 'You're so stupid.' I stopped and turned to look at him. My inner voice asked, 'WTF are you doing with this mess of a dude?' I walked out of the airport and left him there." —MossAvenger 8."I walked in on him going down on my male cousin! I'm a woman, I'm straight, and I thought he was too!" —onebadassMoMo 9."He asked why it had taken me 21 minutes to go to the shop for milk when he's timed it at 16 minutes. He asked me 'Who were you talking to?' Yeah, screw off." —TheBikerMidwife 10."He screamed at the waitress because his steak was medium-well instead of medium. I walked straight out of that restaurant, blocked his number, and never looked back. Anyone who treats service workers like that isn't getting a second chance." —plushyNprecious 11."We refinanced our house to pay off credit card debt. Six months later, I got on the computer and saw she hadn't closed Windows, and saw she was back up to $20K in credit card debt. I packed my stuff the next day, gave her the option of keeping the house in her name or moving out. She chose to stay. One year later, she was forced to sell to pay off her debts." —ab17801 12."I broke up with him immediately after he unilaterally cancelled the couple's therapy sessions I'd planned for us. This is the second time he did this after I'd made clear this was the single most important thing for me and after he'd agreed to the sessions." —Exotic-Bathroom4875 13."When they 'forgot' to tell me their 'crazy' ex-boyfriend was actually their current husband. PEACE." —mothershipq 14."He voted for Trump. He hid it the entire eight months we were together. He knew I was a vocal feminist as he followed me online for years. He made a few misogynistic 'jokes' here and there to get a reaction out of me. He was constantly trying to debate with me. When I look back, I think he thought it would be an ego boost to belittle and 'conquer' a feminist." —Prudent-Ad8731 15."He had the audacity to tell me he was jealous that someone got to have sex with me when I was skinnier." —diddydidit333 16."She stole drugs from someone she definitely shouldn't have, and I had to smooth things over, which resulted in me almost getting shot. The second I got back to the house I told her to get her crap and get out and never looked back." —dman2316 17."He wished death upon the 'old hags who live next door, ruining his life,' because someone had asked the building supervisor to go talk to him about the noise. He was having a house party with loud music blasting through open windows at 11:30 p.m. on a Tuesday." —Nana-stole-my-banana 18."An ex cheated on me while I was going through heart surgery. I dumped him instantly. A lesson I needed to learn and I learnt it well." —kleosailor 19."We went to a concert, I was meeting his friends for the first time. He got insanely drunk before it, but he had told me he'd been sober for two years. He called me his ex's name and then told me to screw I did. He begged for forgiveness, but I'm not risking my peace." —JenNjuic3 finally "I was already pretty done with the relationship due to soooo many other things, but when my grandma died, he told me I shouldn't be 'that sad' because she lived in another country and I didn't get to spend much time with her anyway." —Previous-Egg8682
Forbes
3 hours ago
- Forbes
Silent Breach Exposes 16 Billion Passwords: 5 Things You Must Do Now
A staggering 16 billion passwords were exposed in a silent, decentralized breach compiled from years ... More of malware activity — an unseen cyber threat now looming over governments and tech giants alike. picture alliance via Getty Images While the cybersecurity world was focused on usual suspects like ransomware gangs, nation-state espionage and zero-day exploits, something massive happened in the background. A credential leak of staggering proportions quietly spilled onto the open internet. No ransom note. No press release. No named corporate victim. Just a silent detonation of more than 16 billion individual records containing usernames and passwords for Apple, Google, Microsoft, Facebook and government accounts across 29 countries. Let that sink in. Sixteen billion login records. The scope of this breach eclipses almost every known hack to date. Yet most people have never heard about it. On June 26 2025, researchers at Cybernews revealed that they had discovered 30 unsecured datasets containing over 16 billion records. These were not theoretical vulnerabilities. These were usernames and passwords that provide real access to real systems. The data included everything from private citizen logins to accounts tied to government domains. Facebook, Telegram, Instagram, PayPal, Discord, Roblox — no platform seemed untouched. The data was formatted exactly as infostealing malware delivers it: a string of website URLs, usernames and passwords scraped from infected machines over time. And it was found online, publicly accessible for a period of time before being locked down. One of the earlier warnings came from cybersecurity researcher Jeremiah Fowler, who in May uncovered 47GB of data with 184 million records, sitting in the open on an Elasticsearch server. The server was hosted by World Host Group, a global web hosting provider. Once alerted, the company disabled access and confirmed the server had been spun up by a fraudulent user. But the damage had already been done. 'This is probably one of the weirdest ones I've found in many years,' Fowler told Wired . 'As far as the risk factor here, this is way bigger than most of the stuff I find, because this is direct access into individual accounts. This is a cybercriminal's dream working list.' It wasn't just tech companies that were implicated. Fowler found 220 government email addresses from more than two dozen countries, including the United States, United Kingdom, Canada, India, Israel and Australia. May 2025 : Fowler discovers 184 million exposed records, including government and enterprise credentials, and immediately notifies the hosting provider. : Fowler discovers 184 million exposed records, including government and enterprise credentials, and immediately notifies the hosting provider. Early June 2025 : World Host Group disables the server. No further public comment or disclosure from affected entities. : World Host Group disables the server. No further public comment or disclosure from affected entities. Mid-June 2025: Cybernews publishes a report about the larger aggregation of 30 databases, revealing the total exposure: 16 billion credentials. Unlike high-profile hacks with clear attribution and corporate response, this breach is fragmented. It is the byproduct of years of careless digital hygiene, cybercriminal harvesting and the steady drip of malware-infected machines feeding stolen credentials into dark web markets. How It Happened: Death By A Thousand Infostealers This was not a hack in the conventional sense. No firewalls were breached. No zero-day vulnerabilities were exploited. Instead, the records were compiled over years using infostealer malware. Infostealer malware is a class of malicious software that silently lifts login credentials from infected devices. Christiaan Beek of Rapid7 noted that the data showed 'a lot of overlap' and was 'a combination of old and new' credentials, adding that the aggregation itself posed a serious threat. 'It reflects around 30 separate breaches, stealer logs compiled over years,' he said. Much of the leaked content appears to come from previously compromised password dumps. But according to Cybernews, the presence of fresh infostealer logs makes this breach 'particularly dangerous for organizations lacking multi-factor authentication or credential hygiene practices.' Why This Leak Hasn't Made Headlines Despite its unprecedented scale, this breach has flown under the radar, unlike the United Natural Foods hack, which triggered widespread headlines. One reason is that no single company was directly compromised. There was no named victim, no regulatory filing and no incident response to point to. The data was quietly compiled over years through malware infections and older breaches, then briefly exposed on an unmanaged server. Without a clear villain or breach notification, traditional media had little to latch onto. They couldn't point to one actor or failure. In truth, we are all to blame. Many of the records were previously stolen which led some to dismiss the incident as old news. But that misses the point. The true threat lies in the scale, the recency and the way this data can now be weaponized by attackers against organizations that have not enforced basic security practices. Further, just because the records were previously stolen, a significant percentage were still active. The Bigger Picture: What We Are Doing Wrong This breach was not about a single company failing. It was about everyone failing. As security analyst Chester Wisniewski of Sophos put it, 'These massive dumps are typically just a recycled pile of credentials with a few new ones sprinkled in.' But even old passwords still work when users reuse them. When organizations fail to enforce password resets. When there is no MFA. And therein lies the danger. Infostealer malware is doing exactly what it was built to do: harvest credentials from unprotected machines. The real problem is how unprepared the world remains to stop it. What Needs To Happen Now This is a five-alarm fire for anyone not practicing basic cybersecurity hygiene. Sixteen billion records are now in circulation. Many are still active. Some are tied to government systems. And nearly all were exposed without any one company triggering the alarm. This should be a wake-up call not just for IT departments, but for every executive and individual who relies on digital tools to function. This is not the time to assume you're safe. This is the time to act. Five Immediate Actions For Individuals: Change your passwords across all platforms: Start with your primary email, banking and social media accounts. If you use the same password in multiple places, change every one of them. Password reuse is the single biggest vulnerability exploited in these kinds of leaks. Use unique passwords for every service: One password per account. No exceptions. This ensures that if one login is compromised, the rest remain safe. Use a password manager if you need help generating or storing them. Enable multi-factor authentication on every account that allows it: MFA is no longer optional. Even a simple text message code can stop an attacker with your password. Wherever possible, use app-based or hardware key MFA for stronger protection. Scan your devices for malware, especially infostealers: This data did not appear out of nowhere. It was harvested from infected machines. If you have not scanned your device recently, or if you have never run anti-malware software, now is the time. Infostealers run silently in the background, siphoning off your credentials without leaving a trace. Monitor account activity for unauthorized access: Watch for unfamiliar logins, password reset attempts, or new devices on your accounts. Most services provide tools to review recent activity. Use them. Set up alerts for suspicious behavior. If anything looks off, change your credentials immediately. Five Immediate Actions For Businesses And IT Leaders: Deploy Endpoint Detection and Response tools: Infostealer malware thrives on unmanaged or poorly protected endpoints. EDR tools allow your security team to detect, isolate and remediate these threats in real time before they cause widespread damage. Enforce password managers and centralized identity platforms: Encourage or even better, mandate the use of enterprise-grade password managers. Combine that with Single Sign-On and identity federation to reduce the number of credentials employees must manage and attackers can steal. Conduct ongoing employee security training: One-time training is not enough. Phishing and credential theft are constantly evolving. Organizations need to build a culture of cybersecurity awareness that reinforces good behavior, simulates attacks and rewards vigilance. Implement real-time credential leak monitoring and dark web scanning: Do not wait for a breach notification. Be proactive. Invest in services that scan known dark web marketplaces and data dumps for your domains, employee emails and customer credentials. When a match is found, move fast to rotate access and contain the risk. Apply Access Controls Based on Risk, Not Convenience: Implement role-based access and least privilege policies. Restrict administrative access to only those who absolutely need it. Too many organizations default to broad permissions, giving attackers more room to move once they are inside. Aligning access with actual job function reduces the blast radius when credentials are compromised. The playbook is not complicated. But it does require discipline and urgency. The organizations that act now will be the ones still standing when the next wave of credential-based attacks begins. Compliance Is the Starting Line, Not the Finish Too many organizations mistake compliance for security. Checking the box on a framework does not stop infostealer malware. But it does give you a baseline. Compliance is the first signal that your organization is taking security seriously. It offers structure, policy and governance. But it must be paired with continuous improvements, proactive monitoring and threat intelligence. Treating compliance as the finish line is like bolting your front door while leaving all the windows wide open. A Sobering Reminder This breach should be a sobering reminder that we are losing the war on credentials. Sixteen billion of them just got dumped onto the internet. Some old. Some new. All dangerous. And the biggest threat may not be the data itself, but how few people noticed. If this breach did not reach your radar, let it serve as a wake-up call. If your organization is still relying on usernames and passwords without MFA or threat monitoring, you are playing defense without a helmet. The calculous has now changed. Cybercriminals are not just breaking in. They are now logging in.
Politico
13 hours ago
- Politico
Sheriff says 2 killed after Idaho firefighters shot near Coeur d'Alene
Authorities say a suspect shot at firefighters responding to fire near Coeur d'Alene, Idaho, and the sheriff said two people were killed and police were still 'taking sniper fire' Sunday afternoon. The Kootenai County Sheriff's Office said crews responded to a fire at Canfield Mountain around 1:30 p.m. and gunshots were reported about a half hour later. It was unclear if anyone was shot. Gov. Brad Little said 'multiple' firefighters were attacked. 'This is a heinous direct assault on our brave firefighters,' Little said aid on the social platform X. 'I ask all Idahoans to pray for them and their families as we wait to learn more.' The sheriff's office in neighboring Soshone County said on Facebook that authorities were 'dealing with an active shooter situation where the shooter is still at large.' An alert by the Kootenai County Emergency Management Office asked people to avoid the area around Canfield Mountain Trailhead and Nettleton Gulch Road, about 4 miles north of downtown Coeur d'Alene. The fire was still burning. No additional details were provided. Coeur d'Alene is a city of 55,000 residents near the border with Washington.
