Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Researchers described how malware could abuse an authorized GitHub Actions workflow to obtain an npm publishing credential, but they did not report a confirmed npm Trusted Publishing vulnerability or evidence that 1,500+ packages were exposed. The findings concern a targeted attack path and separate incidents with distinct package counts.
What researchers found—and what they did not
In an August 2026 analysis, Palo Alto Networks’ Unit 42 described ChainDrop, a self-propagating npm worm that infected over 400 packages. The report also outlined a narrowly targeted method for obtaining an npm publishing credential through GitHub Actions OpenID Connect (OIDC). Unit 42 said it did not observe that specific method execute. Its report therefore describes an implemented capability, not a confirmed mass takeover through a flaw in npm Trusted Publishing.
The figure in the headline claim—1,500+ npm packages—is not substantiated by the incident reports summarized here. Counts from separate campaigns should not be added together or presented as evidence of that claim:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors- Over 400 packages: Unit 42’s count for packages infected by ChainDrop in its 2026 analysis.
- 32 packages: Red Hat’s count of compromised
@redhat-cloud-servicespackages in a separate May 2026 incident. - More than 500 packages removed: GitHub’s September 22, 2025 account of its response to the separate Shai-Hulud incident.
These are different incidents, reported by different organizations. None establishes that npm Trusted Publishing itself was vulnerable or that 1,500+ packages were exposed.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
How the targeted Trusted Publishing path worked
npm Trusted Publishing replaces a long-lived publishing token in a supported CI/CD setup with a short-lived credential obtained through an OIDC trust relationship. The registry trusts a configured provider and workflow; the workflow can then request access for an authorized publishing action. That reduces reliance on reusable write tokens, but it does not make a compromised workflow safe.
Unit 42 said ChainDrop could search GitHub Actions runner memory for OIDC tokens and runner secrets. Its report also described a separate, conditional path: malware checked for GitHub Actions, a repository name containing /opensearch-js, and a workflow reference containing release-drafter.yml. If those conditions matched, it could request an OIDC token with npm’s registry audience and exchange it for an npm publishing credential. The researchers said this path was limited to that repository/workflow context and was not observed executing.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
In the described scenario, an attacker who can cause code to run in the authorized release workflow may be able to act with that workflow’s publishing identity. That is a risk in the relationship between the workflow, runner and package permissions—not proof that the registry’s trust mechanism was bypassed.
What provenance proves—and what it cannot
For eligible releases, provenance records information about the repository and workflow that produced a package tarball. npm’s documentation, accessed October 13, 2026, says it automatically generates provenance for Trusted Publishing releases from GitHub Actions or GitLab CI/CD when both the repository and package are public. It says CircleCI Trusted Publishing does not currently include provenance, and provenance is not generated for private repositories.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Provenance is evidence of origin and build identity, not a security verdict on the code. Unit 42 put the distinction plainly: “This is not forged provenance. The attestation says the tarball was built in that repository by that workflow, and that is true.” If an attacker controls or injects code into that workflow, an attestation can accurately identify the compromised workflow while the resulting package is still malicious.
Current npm Trusted Publishing requirements and settings
As documented by npm on October 13, 2026, Trusted Publishing supports GitHub Actions, GitLab CI/CD and CircleCI. The documented minimums are npm CLI 11.5.1 and Node.js 22.14.0; self-hosted runners are not supported. Requirements and configuration behavior can change, so check npm’s live documentation and package settings when setting up a release pipeline.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
npm’s documented action defaults also depend on when a configuration was created:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Configurations created before May 20, 2026 were automatically allowed to use
npm publish. - Configurations created before September 3, 2026 required explicit selection of at least one allowed action.
- For newer configurations, the default is
npm stage publish; direct publishing can be selected instead.
These dates matter when auditing an existing publisher: do not assume a configuration has today’s default. Check which actions its trusted publisher is actually allowed to perform.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
How to reduce publishing risk
- Inspect the trusted publisher configuration. In the npm package settings, confirm the expected provider, repository and workflow identity, and check whether the allowed action is direct publishing or staged publishing.
- Protect the release workflow and runner. Restrict who can change release workflow files, review dependencies and workflow changes, and prevent untrusted pull-request code from running with access to release credentials or privileged runner resources.
- Move to OIDC where supported, then remove unnecessary tokens. npm recommends Trusted Publishing in place of long-lived write tokens when available. Test the OIDC setup first, then restrict token publishing and revoke automation tokens that are no longer needed.
- Consider staged releases. Stage-only permissions route a CI release through
npm stage publish. A maintainer can review it and approve publication with two-factor authentication (2FA), adding a human gate before it becomes public. - Use layered controls. npm’s maximum-security guidance pairs Trusted Publishing with requiring 2FA and disallowing tokens. OIDC limits reliance on reusable credentials, but the workflow and runner still need protection.
What to do if a package or workflow may be compromised
Start by identifying affected package versions and release workflows. Review unexpected npm releases, repository changes and publishing activity; inspect developer endpoints and CI runners for signs of credential theft or unauthorized code execution. Remove affected package versions where appropriate, and revoke or rotate credentials that may have been accessible to the affected systems—including npm, GitHub, cloud, SSH and automation credentials. These steps reflect Unit 42’s recommendations for investigating a suspected ChainDrop compromise; the response should be tailored to the systems and credentials involved.
Separate incidents illustrate why attribution matters. Red Hat’s bulletin says a compromised account, accessed through a malicious VS Code extension, was used to inject code into repositories and publish 32 of its npm packages on May 29, 2026. Red Hat said no released product builds contained a compromised package and that it closed the incident on June 17, 2026. In 2025, GitHub said it removed more than 500 compromised packages after notification of the Shai-Hulud attack on September 14. Neither report is evidence for the 1,500+ figure or a vulnerability in npm Trusted Publishing.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
