Supply Chain Attack Hits AsyncAPI npm Packages

Security researchers from OX Security, SafeDep, Socket, and StepSecurity have flagged four compromised packages in the AsyncAPI npm namespace. The affected packages are @asyncapi/generator-helpers@1.1.1, @asyncapi/generator-components@0.7.1, @asyncapi/generator@3.3.1, and @asyncapi/specs (versions 6.11.2 and 6.11.2-alpha.1).

These packages were not just tampered with — they were weaponized to deliver a multi-stage botnet loader. The attack is a stark reminder that even well-maintained open-source projects can become vectors for malware when credentials fall into the wrong hands.

How the AsyncAPI Malware Worked

The malicious code was hidden in the package tarballs, not in the source repositories. This is a classic supply chain trick: the code looked legitimate on GitHub, but the published npm artifacts contained the payload.

Once installed, the loader executed a multi-stage process. It reached out to a command-and-control server to fetch additional payloads, which could include anything from DDoS bots to credential stealers. The researchers noted that the malware was designed to persist on the infected system, making it particularly dangerous for CI/CD environments where these packages are often installed.

Stage One: The Initial Payload

The first stage involved a script that ran during package installation (the “preinstall” hook). This script decoded a hidden blob and executed it, establishing a foothold on the machine.

Stage Two: Botnet Recruitment

The second stage downloaded a botnet client from a remote server. This client connected to a centralized controller, allowing the attackers to issue commands to all infected machines at once.

Who Was Affected and What to Do

Anyone who installed these specific versions of the AsyncAPI packages between the time of the compromise and the discovery is at risk. The affected versions are:

• @asyncapi/generator-helpers@1.1.1
• @asyncapi/generator-components@0.7.1
• @asyncapi/generator@3.3.1
• @asyncapi/specs@6.11.2 and 6.11.2-alpha.1

If you have any of these in your project, you should immediately audit your lock files, rotate any credentials that might have been exposed, and scan for unusual outbound network connections. The npm registry has since removed the malicious versions, but that doesn’t help if you already pulled them down.

Lessons for Open Source Maintainers

This incident underscores a few hard truths. First, publishing to npm requires more than just strong passwords — two-factor authentication is non-negotiable. Second, maintainers should consider using trusted publishers and signing their packages, so that even if credentials are stolen, the published artifacts can be verified.

For consumers, the lesson is to verify package integrity. Tools like npm audit and lockfile verification can catch some issues, but they won’t catch everything. A healthy dose of skepticism about new versions of critical dependencies is wise.

This isn’t the first time the npm ecosystem has been hit. Similar attacks have targeted other popular packages, and they won’t be the last. The open source supply chain security landscape is evolving, but so are the attackers.

Detection and Response

If you suspect you’ve been compromised, look for these indicators:

• Unexpected network connections from your build servers
• Unusual processes running under the Node.js runtime
• Files created in temporary directories that don’t belong to your project

The researchers have published hashes of the malicious artifacts, so you can cross-check your installed versions. If you find a match, treat it as a security incident — not just a bad dependency.

Botnet malware is particularly nasty because it’s designed to be quiet. It won’t crash your app or throw errors. It just sits there, waiting for commands. That’s why proactive monitoring of your build environment is essential.

In the end, this attack is a reminder that the software supply chain is only as strong as its weakest link. For AsyncAPI users, the fix is straightforward: update to the latest patched versions and review your security posture. For the rest of us, it’s a cautionary tale about the risks we all carry in our node_modules.

The Numbers Behind Oracle’s July 2026 CPU

Oracle has released its July 2026 Critical Patch Update (CPU), and the numbers are staggering. The quarterly security update includes 1,449 patches covering 1,434 unique CVEs across 334 products. It’s one of the largest patch drops in the company’s history.

For context, that’s roughly four times the number of vulnerabilities Oracle typically addresses in a single quarter. And here’s the kicker: a vast majority of these flaws were likely discovered by artificial intelligence, not human researchers.

According to Oracle, only a few dozen of the vulnerabilities were credited to external researchers. The rest were found internally — and the company has been open about its growing reliance on AI to accelerate vulnerability discovery.

What Products Got Patched?

The patch sweep touches nearly every corner of Oracle’s portfolio. Here’s a breakdown of the hardest-hit product families:

• E-Business Suite: 410 patches — the most of any product line
• Fusion Middleware: 355 patches
• Communications: 168 patches
• PeopleSoft: 84 patches

Other products in the update include Database Server, APEX, Autonomous Health Framework, Essbase, GoldenGate, NoSQL Database, SQL Developer, TimesTen In-Memory Database, and a host of industry-specific applications such as Financial Services, HealthCare, Hospitality, Retail, and Utilities.

Java SE, MySQL, JD Edwards, Siebel CRM, and Virtualization products also received fixes. If your organization runs any Oracle software, there’s a good chance it’s in this update.

Remote Exploitation and Critical Severity

Roughly 600 of the patches address vulnerabilities that can be exploited remotely without authentication. That’s a serious concern — these are the flaws attackers can weaponize without needing any prior access to your systems.

Hundreds of the security holes have been assigned a critical severity rating, meaning they could lead to complete system compromise if exploited. The risk profile here is about as high as it gets for an enterprise software vendor.

AI’s Growing Role in Vulnerability Discovery

Oracle revealed earlier this year that it has access to top-tier AI systems, including Anthropic‘s Claude Mythos and OpenAI‘s most capable models. The company is using these tools to speed up and sharpen vulnerability discovery and patching across its own software, Oracle Health, and the open source components it relies on.

The result? A patch cycle where AI found the vast majority of the flaws. This shift has big implications for how we think about software security. If AI can find thousands of vulnerabilities in a single quarter, what does that mean for the attackers using similar tools?

Why You Should Patch Now

Oracle’s patch release isn’t just a routine maintenance task. Threat actors actively exploit Oracle product vulnerabilities in their attacks. Recent examples include the exploitation of a PeopleSoft zero-day and a previously patched EBS vulnerability that hit Estée Lauder.

Organizations running Oracle software should treat this CPU as a priority. Install the patches as soon as possible — ideally within days, not weeks. The window between patch release and exploitation is shrinking, and AI is making it even shorter.

If you’re managing Oracle environments, this is also a good time to review your vulnerability management process and ensure you have visibility into all Oracle products in your infrastructure. The breadth of this update — 334 products — means there’s a real chance something in your environment is affected.

For more on recent Oracle security issues, check out our coverage of Oracle’s monthly security updates and the Zimbra critical vulnerabilities that were patched recently.

The Flaw That Wouldn’t Stay Dead

Here’s a scenario straight out of a security team’s nightmare: you patch a critical vulnerability, breathe a sigh of relief, and then discover the fix didn’t actually stick. That’s exactly what happened with N-able‘s N-central remote monitoring platform.

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Monday added a high-severity flaw to its Known Exploited Vulnerabilities (KEV) catalog after confirming active exploitation in the wild. The vulnerability, tracked as CVE-2026-18577 (CVSS score: 8.2), is a case of incomplete patching for an earlier bug, CVE-2026-18556.

In plain English? The original patch for CVE-2026-18556 didn’t fully address the root cause. Attackers found the gap, and now customers are paying the price.

What Exactly Is CVE-2026-18577?

CVE-2026-18577 is a high-severity vulnerability in N-able N-central, a widely used remote monitoring and management (RMM) platform. Managed service providers (MSPs) rely on it to monitor and manage thousands of endpoints across client networks. That makes this a juicy target for attackers.

The flaw is rooted in incomplete patching. When N-able released a fix for CVE-2026-18556, they addressed the most obvious attack vector but left a secondary path open. CVE-2026-18577 exploits that leftover gap.

According to CISA’s advisory, the vulnerability allows an attacker to achieve remote code execution with high privileges. In the context of an RMM platform, that’s about as bad as it gets. An attacker who compromises N-central can potentially push malicious scripts to every managed device, deploy ransomware, or exfiltrate sensitive data from multiple client networks at once.

Who’s Been Hit?

CISA didn’t name specific victims, but the agency’s decision to add the flaw to the KEV catalog signals real-world impact. The catalog is reserved for vulnerabilities that have been confirmed as actively exploited, not theoretical risks.

Reports indicate that customer environments were compromised before the vulnerability was publicly disclosed. That’s a troubling timeline — it means attackers had a head start. They were exploiting the flaw while defenders were still in the dark.

N-able has since released an updated patch that fully addresses CVE-2026-18577. But the incident raises uncomfortable questions about patch quality and the speed of vulnerability disclosure.

Why the KEV Catalog Matters

For federal agencies, the KEV catalog isn’t optional. Binding Operational Directive (BOD) 22-01 requires all Federal Civilian Executive Branch (FCEB) agencies to remediate KEV-listed vulnerabilities by a specific deadline. CISA typically gives agencies a strict window — often just a few weeks.

For private sector organizations, the KEV catalog serves a different purpose: it’s a prioritization tool. With thousands of vulnerabilities published each year, security teams can’t patch everything immediately. The KEV list tells you which flaws are actually being exploited right now. That’s actionable intelligence.

If your organization uses N-able N-central, this isn’t a “patch when you get around to it” situation. This is a “drop everything and patch now” situation.

What You Need to Do Right Now

• Verify your N-central version. Check if your deployment is affected by CVE-2026-18577. N-able’s advisory lists the specific versions that are vulnerable.
• Apply the latest patch immediately. The updated fix fully addresses the incomplete patching issue. Don’t assume a previous patch covers you.
• Audit for signs of compromise. If you applied the original patch for CVE-2026-18556, there’s a chance attackers could have slipped through. Look for unusual admin activity, unexpected script executions, or new user accounts.
• Monitor N-central logs. Pay special attention to authentication attempts and remote command execution events.

MSPs should also notify their clients about the risk. If you manage other organizations’ networks through N-central, a compromise of your RMM tool could cascade into their environments. Transparency is key.

The Bigger Lesson: Patches Aren’t Always the End

This incident is a stark reminder that patching isn’t a one-and-done activity. Incomplete fixes create a dangerous false sense of security. Teams apply a patch, mark the vulnerability as resolved, and move on. But if the patch was flawed, the risk persists — silently.

Security researchers have long argued for more rigorous patch verification. The N-able case is a textbook example of why that matters. A vulnerability that should have been closed stayed open, and attackers exploited it.

For defenders, the takeaway is simple: after applying a critical patch, verify that it actually works. Test the specific attack vector that the patch was supposed to block. Don’t just trust the vendor’s word.

CISA’s KEV catalog addition is a formal acknowledgment of what’s already happening in the wild. If you haven’t patched yet, you’re exposed. If you patched with the original fix, you may still be exposed. The only safe move is to apply the latest update and audit your environment thoroughly.

This isn’t the first time a patch has been incomplete, and it won’t be the last. But for N-able N-central customers, the stakes are particularly high. An RMM platform compromise isn’t just a single incident — it’s a gateway to every system you manage.

Take the warning seriously. Patch, verify, and audit. That’s the only way to stay ahead of attackers who are already exploiting this flaw.