Search/parrot
● Vendor

parrot

Known CVEs
0
Highest CVSS
—
In KEV
0
Vendor
anafi firmware
Connections
8 relationships
Your First GRC Agent: A Red Teamer's Walkthrough
By Maril Vernon, GRC Engineering Evangelist, Anecdotes. Every vendor on every panel right now is saying the word "agentic." But most of them can't explain what actually changes when you stop treating GRC like a filing cabinet and start treating it like a fluid system. I spent years on the offensive side, red and purple teaming, breaking the controls that GRC teams swore were working. Same findings, same gaps, different quarters. So when I tell you agentic AI is about to reshape how GRC operates, I'm not selling you a buzzword. I'm telling you what I'd be paying attention to if I were still trying to get past your controls. Here is the honest version of where this goes, and what one of these agents actually looks like when you build it. What "Agentic" Actually Means Here Automation is not new to GRC. We have been scripting evidence collection and bolting RPA onto workflows for years. The problem is that most of it just moved the busywork around faster. It still produced static artifacts, still ran on a schedule, still answered the only question legacy GRC knows how to ask: "Did this control pass?" An agent is different in three specific ways. It has autonomy, so it acts when a condition is met instead of waiting for a human to kick off a task. It has context, so it works against the actual state of your program rather than a screenshot from last quarter. And it executes multiple steps, so it can analyze, decide, and act in sequence rather than dumping a row into a report for you to deal with later. The systems we are governing have already gone agentic. Cloud is elastic, identity is fluid, infrastructure is ephemeral, AI is non-deterministic, and CI/CD never stops. Attackers figured that out a long time ago but too many compliance programs are still trying to govern real-time systems with point-in-time assumptions. Now, agentic does not mean handing judgment to a stochastic parrot, in fact most of the work should remain deterministic. The model provides reasoning, summarization, and orchestration. Your controls, thresholds, and policy decisions should still come from humans. Frankly, this is one of the best use cases for AI in cybersecurity. GRC is full of high-volume, repeatable work performed against known baselines. That's exactly the kind of problem machines excel at. We already trust AI to help us detect anomalies, prioritize alerts, and sift through mountains of telemetry. Using it to help analysts identify evidence gaps or trace control drift is hardly the radical leap some people make it out to be. Bottom line: AI should not replace judgment. It should give practitioners more opportunities to creatively apply it. Agent Studio is the no-code builder for custom GRC agents. Pick a trigger, describe the task in plain English, and deploy with a full audit trail. Join the early-access program and build your first agent in minutes. Request Early Access Three Things That Actually Change The analyst's job shifts from collecting to managing. Nobody gets into GRC because they dream of chasing screenshots and manually updating spreadsheets. The analyst's job changes, but not in the way people fear. Agents don't turn practitioners into passive supervisors. Agents don't replace practitioners; they give them back the time to apply judgment where it actually matters. Compliance moves from periodic to continuous. Historically, annual and quarterly cycles existed because humans couldn't continuously evaluate every control and every change. Agents dramatically expand that capability, making continuous assessment practical where periodic reviews once were the only option. The moment that constraint goes away, "are we compliant right now" becomes a question you can actually answer, not a snapshot you defend three months after it stopped being true. Trust becomes the bottleneck. Keep in mind: pass/fail is a compliance outcome. Confidence is a security outcome. People underestimate this one because once effort is cheap, the hard question is whether you trust what the agent did and can prove it, or did you simply shift the manual work to the verification tax? That is a governance problem, and it is the one worth your attention. What It Looks Like to Build One Theory is easy to consume and file away. Here is the concrete version, using Anecdotes Agent Studio, which is the no-code builder my team put into early access. The mechanics are the point, so follow the structure even if you use something else. Agent development comes down to three decisions: Pick a trigger. This is the condition that wakes the agent up. It might be a schedule (run every Monday), or it might be an event in your program (a risk level changes, or evidence for a control goes stale past a freshness threshold you set). I prefer event triggers, because they fire the moment something changes instead of waiting for the next scheduled run, which is what makes the monitoring continuous rather than periodic. Describe the work in plain English. You write the instruction the way you would brief a junior analyst, no code needed. Take ISO 27001:2022 control A.8.5, secure authentication. The instruction might read: "When the MFA evidence for A.8.5 is older than 24 hours, query the identity provider for the current MFA enforcement policy, compare it against the organization's required MFA baseline, and if any group has fallen out of enforcement, open a finding and assign a remediation task to the control owner." Start from a prebuilt recipe or write your own. Deploy and watch. Now trace what the agent actually does when that trigger fires. It reads the live MFA policy from your identity provider through the connected plugin (Okta, Entra ID, whatever you run), pulls the current enforcement state for each group, compares it to the A.8.5 baseline you defined, and finds that a newly provisioned admin group was created without an MFA policy attached. It opens a finding, attaches the policy snapshot it pulled as evidence, links it to A.8.5, and assigns remediation to the IAM owner. Each of those steps lands in an execution log: the trigger event, the data it read, the comparison it ran, the decision it reached, and the action it took. That single run is the difference between "we passed A.8.5 at the last assessment" and "A.8.5 is enforced right now, and here is the timestamped evidence." The Part Security People Will Push On (Correctly) If your instinct reading this was "I am not handing compliance decisions to a black box," good. Keep that. Agentic GRC is defensible for one reason: the work is observable. A useful execution log captures the trigger that fired, the exact inputs the agent read, the rule or baseline it evaluated against, the decision it reached and why, the action it took, and the evidence it touched; all timestamped. That record is what lets you reconstruct any decision after the fact and hand it to an assessor without taking the agent's word for anything. Two scoping rules keep it safe. Give the agent least privilege: read-only access to the systems it evaluates, and write access only to the GRC objects it is allowed to create, like findings and tasks. Then gate anything consequential behind a person. Detecting drift and opening a finding can run unattended; closing a risk or marking a control effective should route to a human for sign-off. Plan for the agent being wrong, because a non-deterministic model sometimes will be. If it opens a finding on A.8.5 that turns out to be a false positive, the log shows exactly what it read and concluded, so you fix the instruction instead of guessing. An action you can trace is an action you can reverse, and that is why the log matters more than the model. Where to Start Don't start with your highest-stakes control. Start with the task that is high-toil and low-judgment, the one your team does the same way every week and hates. Think evidence gap detection, extracting findings from audit reports, or generating analysis rules for evidence that has no testing procedure. Prove the pattern there, read the logs, build the trust, then expand. If you want to go deeper on this, it's the whole agenda at the GRC Data & AI Summit 2026 on August 12, a free virtual event where security, risk, and compliance leaders work through what being agent-ready actually requires. Save your spot here. I did not come back to GRC because it was comfortable. I came back because it was unfinished. Agents are the first time the tooling has started to match the speed, scale, and interconnected nature of the systems we're trying to govern. If you want to see what building one feels like, Agent Studio is in early access now. My advice? Build the boring one first. Then tell me what changed. Maril Vernon is a former red and purple team operator and the Principal GRC Engineering Evangelist at Anecdotes. She writes and speaks on GRC Engineering, continuous controls monitoring, and pushing compliance into the same decade as the systems it governs. Sponsored and written by Anecdotes.
bleepingcomputer.comJun 26, 2026extracted
Hacker Conversations: Inti De Ceukelaire, Raging Against the Machine Creatively
Inti De Ceukelaire is chief hacking officer at the Intigriti bug bounty platform, where he has been for the last seven years. But he has been a hacker for much longer. Hacking Inti De Ceukelaire, a Belgian national, did not set out to be a hacker. Like many hackers he was born with the potential to become one and only gradually realized he is one. There is a slight twist to his motivation. Many hackers say they are driven by an insatiable curiosity to understand how something works, and a deep desire to see if they can make it work better. De Ceukelaire’s starting point was slightly different: he couldn’t accept that this something wouldn’t do what he wanted it to do. Hacking was less to improve the ‘thing’ and more to bend it to his will. “I got a rush from feeling challenged. The computer would say ‘No’, and I would think, ‘Well, we’ll see’.” In his own words it was more a case of Rage Against the Machine than simply Stayin’ Alive. He only realized he was a hacker after finding a few bugs in Google when he was 15. He reported them to Google and got a polite response. Without knowing they were talking to a 15-years old kid, Google emailed him and fixed the bugs in around a week. “I was fifteen years old and talking to a Google engineer. It was the first time in my life I felt like an adult. And a hacker.” A year or so later he found a vulnerability in one of Metallica’s websites (“I was a big fan when I was younger and still had hair – lots of it.”) He reported the flaw and was again treated with courtesy – perhaps a bit more than courtesy. He was invited on stage with the band in front of thousands of fans, and they signed his keyboard. “I got myself on stage with Metallica. I was living my dreams.” In 2018, he found a weakness in the Vatican news website. He reported it – twice. The site did nothing, so he exploited it. Not in a harmful way, but one that would certainly be noticeable. He planted a news announcement stating, “Pope Francis is excited to announce the discovery of Heaven on Earth: Aaist [a town in Belgium] … Therefore, we shall now refer to The Lord as An Onion, named after the nickname of the inhabitants of this blessed city.” A key factor in all of this is that he caused no harm with his hacking skill. He never did anything for personal gain – except, he admits, for one time. It was while still at school. He had a project with an online deadline. He missed the deadline by three seconds; so, he hacked in and changed his submission time by three seconds. He reported himself to his teachers who were, to say the least, understanding. They allowed the hacked time to stand as the real time. And despite his ‘do no harm’ honor, he has a criminal record. “Ten years ago, I reported a very serious vulnerability to a large organization and asked them to thank me and fix it. They blamed the messenger, and it ended up in court.” Technically, he was guilty of hacking – how else could he find the flaw? Luckily, the judge accepted that the motive was pure; so, guilty but unpunished. This conflict of potential punishment for acts of benefit are part and parcel of the rise of ‘bug bounties’ as a distinct profession, and may well be instrumental in the path toward his current position as chief hacking officer at the Intigriti bug bounty platform. The hacker Most hackers today learned their trade by hacking the telephone system and talking to other hackers on online bulletin boards. That era is over. Today, there are books and manuals available. De Ceukelaire did neither. Learning from other people and studying books just makes clones of other people and the writers of books. “It doesn’t make you a hacker – it just teaches you how to parrot other people,” he says. He taught himself by first accepting the challenge and then trying to solve it. He had basic technical knowledge and a bit of programming from his school days. “I didn’t study computer science, and although it sounds contradictory, that helped me.” Trial and error was his method; failure was his teacher. “In doing so, I was attempting a lot of things that wouldn’t make much sense to a technical person, but I was still trying it. I was trying to learn from it. I tested assumptions that a normal-thinking engineer would never have made because they would have skipped all those steps I went through while failing. So, I know some technical stuff at a much deeper level than other people, simply because I failed more often.” He doesn’t criticize the more traditional path (“I know a lot of talented people that have just gone the regular routes”) but he thinks they may miss out on one thing. “Learning from books and just talking to other hackers can make you a little lazy. Forcing yourself to learn it on your own by failing more than the average person… I can recommend this to everybody, because that’s where you get the sparks of creativity.” One thing he does have in common with many other hackers is a reluctance to criticize the morality of any other hacker. There are reasons for this. For De Ceukelaire, one is a dislike of labels. “I would rather call myself a hacker than an ethical hacker. Being an ethical hacker is the default so I shouldn’t have to call myself ethical. It’s not like I go to a pharmacist and ask, ‘Are you an ethical pharmacist?’ I think hacking itself is not a crime. You can conduct crimes with hacking, just like you can conduct crimes with driving. But you don’t imply all drivers are criminals just because some cause accidents. That’s why I’ve always tried to avoid labels – in different parts of the world, hackers will be in different moral environments.” It’s an interesting concept, implying that ‘ethics’ is a construct controlled by local politicians and local lawmakers. What is ethical in one country may be malicious in another country – an elite hacker in the GRU is seen as malicious outside of Russia, but patriotic within Russia; and a military hacker in China is behaving ethically to his or her own country. Government hackers from the NSA or GCHQ or Israel or Iran would be considered unethical outside of their own geopolitical sphere. “In their minds, they are doing what they feel is the ethical thing, and there’s no point arguing that. Such people may never be welcome in our community, but that doesn’t mean that they aren’t great hackers. I can respect these people for their technical skills whenever a majestic attack happens. And I’m gonna give it to them, sometimes it is impressive. So, I can learn from them.” Ethical and malicious are variables – the only common denominator is ‘hacker’. But this only really applies to the geopolitical stage – every country still has local hackers targeting local organizations for personal gain. Has De Ceukelaire ever been tempted to use his skills ‘maliciously’ for personal gain? “No, never. It’s never crossed my mind because there’s a sense of honor that goes with these things.” Ethical would seem to be part of his DNA, but genes have a complex relationship with behavior. Nature (genetics from birth) can provide fundamental tendencies for behavior, but this can be affected by environment during life (nurture, provides a fine tuning of genetics). So, the question whether hackers are born or bred will never be satisfactorily answered – it’s probably a unique interaction between the two for every different hacker – making every hacker unique. For De Ceukelaire, it resulted in ‘face the challenge, solve the problem and never do harm’, but not necessarily never manipulate. He recalls a time when he would go to music festivals (remember the Metallica event) where the price of a beer could be extortionate, but you could get one free pint with an entry token. “So, I would go to the beer tent with my token, break it in half and ask for half a pint for half a token. They would take the half token but give me a full pint – leaving me able to get a second pint later with the other half.” Technically, this was social engineering – people hacking, rather than computer hacking. But it’s a good example of his definition of hacking: solving a problem to get what you want, creatively without causing harm. There is another way in which genetics may come into play for a hacker. It’s a bit iffy, but possible. Genes can affect how the brain works. Neurodiversity is a major effect of how the brain works, and statistically it is quite common among hackers. Is De Ceukelaire neurodiverse? “It’s never been diagnosed,” he said. Remember he doesn’t like labels, and he suspects that everyone is both a hacker and neurodiverse to one degree or another. But he does recognize one ‘symptom’. It doesn’t happen all the time, but when he is interested in the subject… “When I get in the zone, I really get in the zone; and time passes very quickly while I’m concentrating.” It’s the hyperfocus secret weapon of neurodivergent hackers. The bounty-hunting hacker Bounty-hunting became mainstream in 2012 with Bugcrowd and HackerOne. These were followed by, for example, YesWeHack (2015) and Intigriti (2016) in Europe. Used correctly, bounty platforms take away the uncertainty of non-malicious hacking. De Ceukelaire technically has a criminal record because the firm he hacked didn’t understand his motives. He doesn’t believe they were specifically trying to silence his message, he thinks they just followed the labels: to know this he must have hacked their system which means he’s a hacker and a criminal with bad intentions; so, they reported him to the authorities. In other cases, well-intentioned hackers who email companies to report bugs are simply ignored. That too, is understandable. If you believe your system is secure and you get an email from an unknown person saying it isn’t, it is easy to dismiss it as a scam email. And, of course, on occasion, ‘ethical’ hackers have had their life turned upside down by aggressive companies (see Rob Dyke and legal bullying). This is the attraction of bug bounty platforms: they can make computer hacking a legal and profitable occupation. Companies can pay less for better results than by employing their own full-time red team pentesters, and hackers can ply their trade in safety. Since rules exist on both sides, companies know that flaws can be discovered and fixed without fearing the hacker is malicious, while hackers have a place and purpose to hack without fear of prosecution, and get paid for their work. Before bug bounties it was easy for a hacker to choose a path of crime. “Why? Because there was no ethical path,” says De Ceukelaire. “I love hacking, I love every single minute of it. I love the chase. I love to see how the technical things come together. But 10 years ago, doing this you were almost always technically committing a crime, however moral your motivations. I would never wish to hurt an individual or a company – I was never an activist, I just wanted to hack. But there was no legal way to do this.” Bug bounties have changed things. “If you live in a western society, there’s now no reason for a hacker to take the criminal path. By doing the right thing, there’s no risk, there’s equal if not better pay, and there’s satisfaction in making things better and not worse. Personally, I work and hack with Intigriti because I want to change the world. I want to get the progressive laws that we have here in Belgium into every single part of the world, and I want that to be the default.” Related: Hacker Conversations: Rachel Tobac and the Art of Social Engineering Related: Hacker Conversations: John Kindervag, a Making not Breaking Hacker Related: Hacker Conversations: Frank Trezza – From Phreaker to Pentester Related: Hacker Conversations: David Kennedy – an Atypical Typical Hacker
securityweek.comMar 4, 2026extracted
Parrot OS shares its 2026 plans for security tools and platform support
Parrot OS shares its 2026 plans for security tools and platform support Parrot OS is a Debian-based Linux distribution built for cybersecurity work. Security practitioners use it for penetration testing, digital forensics, malware analysis, and privacy-focused research. The operating system bundles security tools, development utilities, and privacy features into a maintained platform used in labs, training environments, and day-to-day testing workflows. Current focus areas for the platform Parrot OS development continues to center on maintaining the core operating system and keeping bundled tools aligned with upstream projects. Recent work includes updates to the kernel, desktop environment, and core packages that support daily testing and research tasks. Parrot OS 7.0, released in late 2025, established the baseline for current development. Work planned for 2026 builds on that release with ongoing updates across the main editions and deployment formats used by practitioners. Tooling and platform updates planned for 2026 ParrotSec plans to introduce additional tools that support security testing, research, and development workflows. The roadmap points to continued refinement of existing toolsets alongside the addition of new utilities requested by users and contributors. Platform work for 2026 includes support for lightweight and container-based deployments. ParrotSec also plans to improve compatibility with environments commonly used for virtualization and cloud-based labs, reflecting how practitioners deploy testing systems today. Documentation is another area of planned work. ParrotSec intends to expand written guides and workflow references to help users build repeatable lab environments and integrate Parrot OS into automated testing setups. 2026 vision for AI as an attack surface ParrotSec identifies AI systems as an emerging area of security research and testing. The roadmap describes plans to study how AI technologies fit into offensive and defensive security work, with attention on practical tooling and failure modes. “LLM powered chatbots and agents are becoming part of real-world security workflows and, inevitably, part of real-world attack surfaces. Our goal is to study the tools that test and secure AI systems, understand where they fail, and explore how offensive security techniques translate into this space,” explained Giulia M. Stabile, Director – Marketing & Operations Manager, ParrotSec. This work ties into broader efforts to evaluate how security tools and methodologies apply to AI-driven systems used in production environments. Ongoing role of the community Community involvement remains a central part of Parrot OS development. Users contribute through forums, issue trackers, and documentation repositories where they report bugs, suggest enhancements, and submit code changes. Parrot OS follows a rolling update model, with frequent incremental updates delivered as changes are completed and tested. Snapshots and milestone builds are expected throughout the year as development progresses.
helpnetsecurity.comJan 13, 2026extracted
Chatbots parrot Putin's propaganda about the illegal invasion of Ukraine
ai and ML AI slop is good for business if you know what you're doingYour irresponsibility is someone else's opportunity SAAS Salesforce partners not seeing meaningful revenue from Agentforce AI platform, report saysShow us the money ai and ml AI companies are burning books, advocates complain to FTCFahrenheit 203, the temperature GPUs stop gorging on literature DEVOPS Go updates may delight diehard gophers but displease AI overlordsv 1.27 expands generics to support methods EDGE AND IOT Waymo has designed a robocar chip to stay ahead of Tesla5 nm ML accelerators promise 1,000+ TOPS, ultra-low latency Security Russians are posing as Signal support to launch phishing attacksPLUS: US takes down Iranian propaganda sites; Marketing company asks 'Why Do We Have Your Information?' And more! Security Microsoft patches failed to fix on-prem SharePoint, which is now under zero-day attackPLUS: China upgrades smartphone surveillance tools; Ring eases anti-snooping stance; and more Black Hat and DEF CON DEF CON Franklin project enlists hackers to harden critical infrastructureVoting village reports have been so successful, says Jeff Moss, that the whole of DEF CON will now be included Security EQT buys majority share in Swiss cybersecurity biz AcronisWent at equivalent of $3.5B+ valuation for entire firm, though portion sold not specified Malware Month Ten years since the first corp ransomware, Mikko Hyppönen sees no end in sightOn the plus side, infosec's a good bet for a long, stable career FOSS smashed one Microsoft monopoly. After 20 years of failure, it's time to smash anotherWord up GNOME can look like Windows – and Flashback can do it without extensionsNew 'Simple-taskbar' is an option, but there's a simpler, stabler way A moment of silence, please, for the final release of Debian on x86-32New Debian versions hit FOSSland in the form of 13.6 and 12.15 Baddies caught exploiting extensions bugs with perfect 10 scores on vulnerable Joomla websitesFlaws in iCagenda, Balbooa Forms extensions can impact open source CMS that powers a million sites worldwide Frame: A new X11 server – implemented directly in assemblyJoins yserver, Phoenix, and of course XLibre – and outlier Arcan Cinnamon 6.8 will support Wayland – if you want itNext version of Linux Mint’s desktop has both kinds of display server
go.theregister.comOct 28, 2025extracted
⚡ Weekly Recap: F5 Breached, Linux Rootkits, Pixnapping Attack, EtherHiding & More
It’s easy to think your defenses are solid — until you realize attackers have been inside them the whole time. The latest incidents show that long-term, silent breaches are becoming the norm. The best defense now isn’t just patching fast, but watching smarter and staying alert for what you don’t expect. Here’s a quick look at this week’s top threats, new tactics, and security stories shaping the landscape. ⚡ Threat of the Week F5 Exposed to Nation-State Breach — F5 disclosed that unidentified threat actors broke into its systems and stole files containing some of BIG-IP's source code and information related to undisclosed vulnerabilities in the product. The company said it learned of the incident on August 9, 2025, although it's believed that the attackers were in its network for at least 12 months. The attackers are said to have used a malware family called BRICKSTORM, which is attributed to a China-nexus espionage group dubbed UNC5221. GreyNoise said it observed elevated scanning activity targeting BIG-IP in three waves on September 23, October 14, and October 15, 2025, but emphasized the anomalies may not necessarily relate to the hack. Censys said it identified over 680,000 F5 BIG-IP load balancers and application gateways visible on the public internet, with the majority of hosts located in the U.S., followed by Germany, France, Japan, and China. Not all identified systems are necessarily vulnerable, but each represents a publicly accessible interface that should be inventoried, access-restricted, and patched proactively as a precautionary measure. "Edge infrastructure and security vendors remain prime targets for long-term, often state-linked threat actors," John Fokker, vice president of threat intelligence strategy at Trellix, said. "Over the years, we have seen nation-state interest in exploiting vulnerabilities in edge devices, recognizing their strategic position in global networks. Incidents like these remind us that strengthening collective resilience requires not only hardened technology but also open collaboration and intelligence sharing across the security community." Zero Trust + AI: Thrive in the AI Era and Empower Your Workforce It’s no surprise, hackers are using AI in creative ways to compromise users and breach organizations. Zscaler Zero Trust + AI helps defeat ransomware and AI-power attacks today by enabling you to detect and block advanced threats, and discover and classify sensitive data everywhere. Learn more about Zscaler Zero Trust + AI ➝ 🔔 Top News N. Korea Uses EtherHiding to Hide Malware Inside Blockchain Smart Contracts — North Korean threat actors have been observed leveraging the EtherHiding technique to distribute malware and enable cryptocurrency theft, marking the first time a state-sponsored hacking group has embraced the method. The activity has been attributed to a cluster tracked as UNC5342 (aka Famous Chollima). The attack wave is part of a long-running campaign codenamed Contagious Interview, wherein the attackers approach potential targets on LinkedIn by posing as recruiters or hiring managers, and trick them into running malicious code under the pretext of a job assessment after shifting the conversation to Telegram or Discord. In the latest attack waves observed since February 2025, the threat actors use a JavaScript downloader that interacts with a malicious BSC smart contract to download JADESNOW, which subsequently queries the transaction history associated with an Ethereum address to fetch the JavaScript version of InvisibleFerret. LinkPro Linux Rootkit Spotted in the Wild — An investigation into the compromise of an Amazon Web Services (AWS)-hosted infrastructure led to the discovery of a new GNU/Linux rootkit dubbed LinkPro. The backdoor features functionalities relying on the installation of two extended Berkeley Packet Filter (eBPF) modules to conceal itself and to be remotely activated upon receiving a magic packet - a TCP SYN packet with a specific window size (54321) that signals the rootkit to await further instructions within a one-hour window, allowing it to evade traditional security defenses. The commands supported by LinkPro include executing /bin/bash in a pseudo-terminal, running a shell command, enumerating files and directories, performing file operations, downloading files, and setting up a SOCKS5 proxy tunnel. It's currently not known who is behind the attack, but it's suspected that the threat actors are financially motivated. Zero Disco Campaign Targets Cisco Devices with Rootkits — A new campaign has exploited a recently disclosed security flaw impacting Cisco IOS Software and IOS XE Software to deploy Linux rootkits on older, unprotected systems. The activity, codenamed Operation Zero Disco by Trend Micro, involves the weaponization of CVE-2025-20352 (CVSS score: 7.7), a stack overflow vulnerability in the Simple Network Management Protocol (SNMP) subsystem that could allow an authenticated, remote attacker to execute arbitrary code by sending crafted SNMP packets to a susceptible device. The operation primarily impacted Cisco 9400, 9300, and legacy 3750G series devices, Trend Micro said. The intrusions have not been attributed to any known threat actor or group. Pixnapping Attack Leads to Data Theft on Android Devices — Android devices from Google and Samsung have been found vulnerable to a side-channel attack that could be exploited to covertly steal two-factor authentication (2FA) codes, Google Maps timelines, and other sensitive data without the users' knowledge pixel-by-pixel. The attack has been codenamed Pixnapping. Google is tracking the issue under the CVE identifier CVE-2025-48561 (CVSS score: 5.5). Patches for the vulnerability were issued by the tech giant as part of its September 2025 Android Security Bulletin, with additional fixes forthcoming in December. Chinese Threat Actors Exploited ArcGIS Server as Backdoor — Threat actors with ties to China have been attributed to a novel campaign that compromised an ArcGIS system and turned it into a backdoor for more than a year. The activity is the handiwork of a Chinese state-sponsored hacking group called Flax Typhoon, which is also tracked as Ethereal Panda and RedJuliett. "The group cleverly modified a geo-mapping application's Java server object extension (SOE) into a functioning web shell," ReliaQuest said. "By gating access with a hardcoded key for exclusive control and embedding it in system backups, they achieved deep, long-term persistence that could survive a full system recovery." The attack chain involved the threat actors targeting a public-facing ArcGIS server that was linked to a private, internal ArcGIS server by compromising a portal administrator account to deploy a malicious SOE, thereby allowing them to blend in with normal traffic and maintain access for extended periods. The attackers then instructed the public-facing server to create a hidden directory to serve as the group's "private workspace." They also blocked access to other attackers and admins with a hard-coded key. The findings demonstrate Flax Typhoon's consistent modus operandi of quietly turning an organization's own tools against itself rather than using sophisticated malware or exploits. ️🔥 Trending CVEs Hackers move fast. They often exploit new vulnerabilities within hours, turning a single missed patch into a major breach. One unpatched CVE can be all it takes for a full compromise. Below are this week’s most critical vulnerabilities gaining attention across the industry. Review them, prioritize your fixes, and close the gap before attackers take advantage. This week’s list includes — CVE-2025-24990, CVE-2025-59230 (Microsoft Windows), CVE-2025-47827 (IGEL OS before 11), CVE-2023-42770, CVE-2023-40151 (Red Lion Sixnet RTUs), CVE-2025-2611 (ICTBroadcast), CVE-2025-55315 (Microsoft ASP.NET Core), CVE-2025-11577 (Clevo UEFI firmware), CVE-2025-37729 (Elastic Cloud Enterprise), CVE-2025-9713, CVE-2025-11622 (Ivanti Endpoint Manager), CVE-2025-48983, CVE-2025-48984 (Veeam), CVE-2025-11756 (Google Chrome), CVE-2025-49201 (Fortinet FortiPAM and FortiSwitch Manager), CVE-2025-58325 (Fortinet FortiOS CLI), CVE-2025-49553 (Adobe Connect collaboration suite), CVE-2025-9217 (Slider Revolution plugin), CVE-2025-10230 (Samba), CVE-2025-54539 (Apache ActiveMQ), CVE-2025-41703, CVE-2025-41704, CVE-2025-41706, CVE-2025-41707 (Phoenix Contact QUINT4), and CVE-2025-11492, CVE-2025-11493 (ConnectWise Automate). 📰 Around the Cyber World Microsoft Unveils New Security Improvements — Microsoft revealed that "parts of the kernel in Windows 11 have been rewritten in Rust, which helps mitigate against memory corruption vulnerabilities like buffer overflows and helps reduce attack surfaces." The company also noted that it's taking steps to secure AI-powered agentic experiences on the operating system by ensuring that they operate with limited permissions and only obtain access to resources users' explicitly provide permission to. In addition, Microsoft said agents that integrate with Windows must be cryptographically signed by a trusted source so that they can be revoked if found to be malicious. Each AI agent will also run under its own dedicated agent account that's distinct from the user account on the device. "This facilitates agent-specific policy application that can be different from the rules applied to other accounts like those for human users," it said. SEO Campaign Uses Fake Ivanti Installers to Steal Credentials — A new attack campaign has leveraged SEO poisoning to lure users into downloading a malicious version of the Ivanti Pulse Secure VPN client. The activity targets users searching for legitimate software on search engines like Bing, redirecting them to attacker-controlled lookalike websites (ivanti-pulsesecure[.]com or ivanti-secure-access[.]org). The goal of this attack is to steal VPN credentials from the victim's machine, enabling further compromise. "The malicious installer, a signed MSI file, contains a credential-stealing DLL designed to locate, parse, and exfiltrate VPN connection details," Zscaler said. "The malware specifically targets the connectionstore.dat file to steal saved VPN server URIs, which it combines with hardcoded credentials for exfiltration. Data is sent to a command-and-control (C2) server hosted on Microsoft Azure infrastructure." Qilin's Ties with BPH Providers Exposed — Cybersecurity researchers from Resecurity examined Qilin ransomware group's "close affiliation" with underground bulletproof hosting (BPH) operators, finding that the e-crime actor has not only relied on Cat Technologies Co. Limited. (which, in turn, is hosted on an IP address tied to Aeza Group) for hosting its data leak site, but also advertised services like BEARHOST Servers (aka Underground) on its WikiLeaksV2 site, where the group publishes content about their activities. BEARHOST has been operational since 2016, offering its services for anywhere from $95 to $500. While BEARHOST abruptly announced the stoppage of its service on December 28, 2024, it is assessed that the threat actors have taken the BPH service into private mode, catering only to trusted and vetted underground actors. On May 8, 2025, it resurfaced as Voodoo Servers, only for the operators to terminate the service again towards the end of the month, citing political reasons. "The actors decided to disappear through an 'exit scam' scenario, keeping the underground audience completely clueless," Resecurity said. "Notably, the legal entities behind the service continue their operations." Notably, Cat Technologies Co. Limited. also shares links to shadowy entities like Red Bytes LLC, Hostway, Starcrecium Limited, and Chang Way Technologies Co. Limited, the last of which has been associated with extensive malware activity, hosting command-and-control (C2) servers of Amadey, StealC, and Cobalt Strike used by cybercriminals. Another entity of note is Next Limited, which shares the same Hong Kong address as Chang Way Technologies Co. Limited and has been attributed to malicious activity in connection with Proton66. U.S. Judge Bars NSO Group from Targeting WhatsApp — A U.S. judge barred NSO Group from targeting WhatsApp users and cut the punitive damages verdict awarded to Meta by a jury in May 2025 to $4 million, because the court did not have enough evidence to determine that NSO Group's behavior was "particularly egregious." The permanent injunction handed out by U.S. District Judge Phyllis Hamilton means that the Israeli vendor cannot use WhatsApp as a way to infect targets' devices. As a refresher, Meta sued the NSO Group in 2019 over the use of Pegasus spyware by exploiting a then-zero-day flaw in the messaging app to spy on 1,400 people from 20 countries, including journalists and human rights activists. It was fined close to $168 million earlier this May. The proposed injunction requires NSO Group to delete and destroy computer code related to Meta's platforms, and she concluded that the provision is "necessary to prevent future violations, especially given the undetectable nature of defendants' technology." Google's Privacy Sandbox Initiative is Officially Dead — In 2019, Google launched an initiative called Privacy Sandbox to come up with privacy-enhancing alternatives to replace third-party cookies on the web. However, with the company abandoning its plans to deprecate third-party tracking cookies, the project appears to be winding down. To that end, the tech giant said it's retiring the following Privacy Sandbox technologies citing low levels of adoption: Attribution Reporting API (Chrome and Android), IP Protection, On-Device Personalization, Private Aggregation (including Shared Storage), Protected Audience (Chrome and Android), Protected App Signals, Related Website Sets (including requestStorageAccessFor and Related Website Partition), SelectURL, SDK Runtime and Topics (Chrome and Android). In a statement shared with Adweek, the company said it will continue to work to improve privacy across Chrome, Android, and the web, but not under the Privacy Sandbox branding. Russia Blocks Foreign SIM Cards — Russia said it's taking steps to temporarily block mobile internet for foreign SIM cards, citing national security reasons. The new rule imposes a mandatory 24-hour mobile internet blackout for anyone entering Russia with a foreign SIM card. Flaw in CORS headers in Web Browsers Disclosed — The CERT Coordination Center (CERT/CC) disclosed details of a vulnerability in cross-origin resource sharing (CORS) headers in Chromium, Google Chrome, Microsoft Edge, Safari, and Firefox that enables the CORS policy to be manipulated. This can be combined with DNS rebinding techniques to issue arbitrary requests to services listening on arbitrary ports, regardless of the CORS policy in place by the target. "An attacker can use a malicious site to execute a JavaScript payload that periodically sends CORS headers in order to ask the server if the cross-origin request is safe and allowed," CERT/CC explained. "Naturally, the attacker-controlled hostname will respond with permissive CORS headers that will circumvent the CORS policy. The attacker then performs a DNS rebinding attack so that the hostname is assigned the IP address of the target service. After the DNS responds with the changed IP address, the new target inherits the relaxed CORS policy, allowing an attacker to potentially exfiltrate data from the target." Mozilla is tracking the vulnerability as CVE-2025-8036. Phishing Campaigns Use Microsoft's Logo for Tech Support Scams — Threat actors are exploiting Microsoft's Name and branding in phishing emails to lure users into fraudulent tech support scams. The messages contain links that, when clicked, take the victims to a fake CAPTCHA challenge, after which they are redirected to a phishing landing page to unleash the next stage of the attack. "After passing the captcha verification, the victim is suddenly visually overloaded with several pop-ups that appear to be Microsoft security alerts," Cofense said. "Their browser is manipulated to appear locked, and they lose the ability to locate or control their mouse, which adds to the feeling that the system is compromised. This involuntary loss of control creates a faux ransomware experience, leading the user to believe their computer is locked and to take immediate action to remedy the infection." From there, users are instructed to call a number to reach Windows Support, at which they are connected to a bogus technician to take the attack forward. "The threat actor could exploit further by asking the user to provide account credentials or persuade the user to install remote desktop tools, allowing full access to their system," the company said. Taxpayers, Drivers Targeted in Refund and Road Toll Smishing Scams — A smishing campaign has leveraged at least 850 newly-registered domain names in September and early October to target people living in the U.S., the U.K., and elsewhere with phishing links that use tax refunds, road toll charges, or failed package deliveries as a lure. The websites, designed to be loaded only when launched from a mobile device, claim to provide information about their tax refund status or obtain a subsidy of up to £300 to help offset winter fuel costs (note: this is a real U.K. government initiative), only to prompt them to provide personal details such as name, home address, telephone number and email address, as well as payment card information. The entered data is exfiltrated to the attackers over the WebSocket protocol. Some of the scam websites have also been found to target Canadian, German, and Spanish residents and visitors, per Netcraft. Meta's New Collage Feature May Use Photos in Phone's Camera Roll — Meta is officially rolling out a new opt-in feature to Facebook users in the U.S. and Canada to suggest the best photos and videos from users' camera roll and create collages and edits. "With your permission and the help of AI, our new feature enables Facebook to automatically surface hidden gems – those memorable moments that get lost among screenshots, receipts, and random snaps – and edit them to save or share," the company said. The feature was first tested back in late June 2025. The social media company emphasized that the suggestions are private and that it does not use media obtained from users' devices via the camera roll to train its models, unless users opt to edit the media with their AI tools or publish those suggestions to Facebook. Users who wish to opt out of the feature can do so by navigating Settings and Privacy > Settings > Preferences > Camera Roll Sharing Suggestions. Fake Homebrew, TradingView, LogMeIn Sites Serve Stealer Malware Targeting Macs — Threat actors are employing social engineering tactics to trick users into visiting fake websites impersonating trusted platforms like as Homebrew, TradingView, and LogMeIn, where they are instructed to copy and run a malicious command on the Terminal app as part of ClickFix-style attacks, resulting in the deployment of stealer malware such as Atomic Stealer and Odyssey Stealer. "More than 85 phishing domains were identified, connected through shared SSL certificates, payload servers, and reused infrastructure," Hunt.io said. "The findings suggest a coordinated and ongoing campaign in which operators continuously adapt their infrastructure and tactics to maintain persistence and evade detection within the macOS ecosystem." It's suspected that users are driven to these websites via sponsored ads on search engines like Bing and Google. Dutch Data Protection Watchdog Fines Experian $3.2 Million for Privacy Violations — The Dutch Data Protection Authority (DPA) imposed a fine of €2.7 million ($3.2 million) on Experian Netherlands for collecting data in contravention of the E.U. General Data Protection Regulation (GDPR). The DPA said the consumer credit reporting company gathered information on people from both public and non-public sources and failed to make it clear why the collection of certain data was necessary. In addition to the penalty, Experian is expected to delete the database of personal data by the end of the year. The company has also ceased its operations in the country. "Until January 1, 2025, Experian provided credit assessments about individuals to its clients," the DPA said. "To do this, the company collected data such as negative payment behavior, outstanding debts, or bankruptcies. The AP found that Experian violated the law by unlawfully using personal data." Threat Actors Send Fake Password Manager Breach Alerts — Bad actors are sending phishing alerts claiming that their password manager accounts for 1Password and Lastpass have been compromised in order to trick users into providing their passwords and hijack their accounts. In response to the attack, LastPass said it has not been hacked and that it's an attempt on the part of the attackers to generate a false sense of urgency. In some cases spotted by Bleeping Computer, the activity has also been found to urge recipients to install a more secure version of the password manager, resulting in the deployment of a legitimate remote access software called Syncro. The software vendor has since moved to shut down the malicious accounts to prevent further installs. SocGholish MaaS Detailed — LevelBlue has published an analysis of a threat activity cluster known as SocGholish (aka FakeUpdates), which is known to be active since 2017, leveraging fake web browser update prompts on compromised websites as a lure to distribute malware. Victims are typically routed through Traffic Distribution Systems (TDS) like Keitaro and Parrot TDS to filter users based on specific factors such as geography, browser type, or system configuration, ensuring that only the intended targets are exposed to the payload. It's offered under a malware-as-a-service (MaaS) by a financially motivated cybercrime group called TA569. SocGholish stands out for its ability to turn legitimate websites into large-scale distribution platforms for malware. Acting as an initial access broker (IAB), its operations profit from follow-on compromises by other actors. "Once executed, its payloads range from loaders and stealers to ransomware, allowing for extensive follow-up exploitation," LevelBlue said. "This combination of broad reach, simple delivery mechanisms, and flexible use by multiple groups makes SocGholish a persistent and dangerous threat across industries and regions." One of its primary users is Evil Corp, with the malware also used to deliver RansomHub in early 2025. 🎥 Cybersecurity Webinars The Practical Framework to Govern AI Agents Without Slowing Innovation → AI is changing everything fast — but for most security teams, it still feels like a fight just to keep up. The goal isn’t to slow innovation with more controls; it’s to make those controls work for the business. By building security into AI from the start, you can turn what used to be a bottleneck into a real accelerator for growth and trust. The Future of AI in GRC: Turning Risk Into a Compliance Advantage - AI is changing how companies manage risk and compliance — fast. It brings big opportunities but also new challenges. This webinar shows you how to use AI safely and effectively in GRC, avoid common mistakes, and turn complex rules into a real business advantage. Workflow Clarity: How to Blend AI and Human Effort for Real Results - Too many teams are rushing to “add AI” without a plan — and ending up with messy, unreliable workflows. Join us to learn a clearer approach: how to use AI thoughtfully, simplify automation, and build systems that scale securely. 🔧 Cybersecurity Tools Beelzebub - It turns honeypot deployment into a powerful, low-code experience. It uses AI to simulate real systems, helping security teams detect attacks, track emerging threats, and share insights through a global threat intelligence network. NetworkHound - It maps your Active Directory network from the inside out. It discovers every device — domain-joined or shadow-IT — validates SMB and web services, and builds a full BloodHound-compatible graph so you can see and secure your environment clearly. Disclaimer: These tools are for educational and research use only. They haven’t been fully security-tested and could pose risks if used incorrectly. Review the code before trying them, test only in safe environments, and follow all ethical, legal, and organizational rules. 🔒 Tip of the Week Most Cloud Breaches Aren’t Hacks — They’re Misconfigurations. Here’s How to Fix Them — Cloud storage buckets like AWS S3, Azure Blob, and Google Cloud Storage make data sharing easy — but one wrong setting can expose everything. Most data leaks happen not because of hacking, but because someone left a public bucket, skipped encryption, or used a test bucket that never got locked down. Cloud platforms give you flexibility, not guaranteed safety, so you need to check and control access yourself. Misconfigurations usually happen when permissions are too broad, encryption is disabled, or visibility is lost across multiple clouds. Doing manual checks doesn’t scale — especially if you manage data in AWS, Azure, and GCP. The fix is using tools that automatically find, report, and even fix unsafe settings before they cause damage. ScoutSuite is a strong starting point for cross-cloud visibility. It scans AWS, Azure, and GCP for open buckets, weak IAM roles, and missing encryption, then creates an easy-to-read HTML report. Prowler goes deeper into AWS, checking S3 settings against CIS and AWS benchmarks to catch bad ACLs or unencrypted buckets. For ongoing control, Cloud Custodian lets you write simple policies that automatically enforce rules — for example, forcing all new buckets to use encryption. And CloudQuery can turn your cloud setup into a searchable database, so you can monitor changes, track compliance, and visualize risks in one place. The best approach is to combine them: run ScoutSuite or Prowler weekly to find issues, and let Cloud Custodian handle automatic fixes. Even a few hours spent setting these up can stop the kind of data leaks that make headlines. Always assume every bucket is public until proven otherwise — and secure it like it is. Conclusion The truth is, no tool or patch will ever make us fully secure. What matters most is awareness — knowing what’s normal, what’s changing, and how attackers think. Every alert, log, or minor anomaly is a clue. Keep connecting those dots before someone else does.
thehackernews.comOct 20, 2025extracted
SocGholish Malware Spread via Ad Tools; Delivers Access to LockBit, Evil Corp, and Others
The threat actors behind the SocGholish malware have been observed leveraging Traffic Distribution Systems (TDSs) like Parrot TDS and Keitaro TDS to filter and redirect unsuspecting users to sketchy content. "The core of their operation is a sophisticated Malware-as-a-Service (MaaS) model, where infected systems are sold as initial access points to other cybercriminal organizations," Silent Push said in an analysis. SocGholish, also called FakeUpdates, is a JavaScript loader malware that's distributed via compromised websites by masquerading as deceptive updates for web browsers like Google Chrome or Mozilla Firefox, as well as other software such as Adobe Flash Player or Microsoft Teams. It's attributed to a threat actor called TA569, which is also tracked as Gold Prelude, Mustard Tempest, Purple Vallhund, and UNC1543. Attack chains involve deploying SocGholish to establish initial access and broker that compromised system access to a diverse clientele, including Evil Corp (aka DEV-0243), LockBit, Dridex, and Raspberry Robin (aka Roshtyak). Interestingly, recent campaigns have also leveraged Raspberry Robin as a distribution vector for SocGholish. "SocGholish infections typically originate from compromised websites that have been infected in multiple different ways," Silent Push said. "Website infections can involve direct injections, where the SocGholish payload delivery injects JS directly loaded from an infected webpage or via a version of the direct injection that uses an intermediate JS file to load the related injection." Besides redirecting to SocGholish domains via compromised websites, another primary source of traffic involves using third-party TDSes like Parrot TDS and Keitaro TDS to direct web traffic to specific websites or to landing pages after performing extensive fingerprinting of the site visitor and determining if they are of interest based on certain predefined criteria. Keitaro TDS has long been involved in threat activity going beyond malvertising and scams to deliver more sophisticated malware, including exploit kits, loaders, ransomware, and Russian influence operations. Last year, Infoblox revealed how SocGholish, a VexTrio partner, used Keitaro to redirect victims to VexTrio's TDSes. "Because Keitaro also has many legitimate applications, it is frequently difficult or impossible to simply block traffic through the service without generating excessive false positives, although organizations can consider this in their own policies," Proofpoint noted back in 2019. Keitaro TDS is believed to be connected to TA2726, which has functioned as a traffic provider for both SocGholish and TA2727 by compromising websites and injecting a Keitaro TDS link, and then selling that to its customers. "The intermediate C2 [command-and-control] framework dynamically generates payloads that victims download at runtime," Silent Push noted. "It is essential to note that across the execution framework, from the initial SocGholish injection to the on-device execution of the Windows implant, the entire process is continuously tracked by SocGholish's C2 framework. If, at any time, the framework determines that a given victim is not 'legitimate,' it will stop the serving of a payload." The cybersecurity company has also assessed that there are possibly former members who are involved in Dridex, Raspberry Robin, and SocGholish, given the overlapping nature of the campaigns observed. The development comes as Zscaler detailed an updated version of Raspberry Robin that features improved obfuscation methods, changes to its network communication process, and embeds pointing to intentionally corrupted TOR C2 domains, signaling continued efforts to avoid detection and hinder reverse engineering efforts. "The network encryption algorithm has changed from AES (CTR mode) to Chacha-20," the company said. "Raspberry Robin has added a new local privilege escalation (LPE) exploit (CVE-2024-38196) to gain elevated privileges on targeted systems." The disclosure also follows an evolution of DarkCloud Stealer attacks that employ phishing emails to deliver a ConfuserEx-protected version of the stealer payload written in Visual Basic 6, which is launched and executed using a technique called process hollowing. "DarkCloud Stealer is typical of an evolution in cyberthreats, leveraging obfuscation techniques and intricate payload structures to evade traditional detection mechanisms," Unit 42 said. "The shift in delivery methods observed in April 2025 indicates an evolving evasion strategy." Fortinet FortiGuard Labs, which also detailed another DarkCloud campaign, said it identified phishing emails that tricked users recipients into opening an attached RAR file under the pretext of providing an urgent quote. The RAR archives contain a JavaScript payload that, when launched, decodes PowerShell responsible for dropping a fileless variant of the stealer via an encrypted DLL embedded within a JPEG image hosted on The Internet Archive. DarkCloud gathers "credentials, payment information stored in web browsers, FTP clients, and email clients," security researcher Xiaopeng Zhang said. "It also collects the email contacts from the victim’s email client software."
thehackernews.comAug 7, 2025extracted