· via Hacker News – Front Page (hnrss.org)
macOS 27.0 quietly adds /pkg/env/global/bin to the default PATH
macOS 27.0 ships a new /etc/paths.d file that inserts /pkg/env/global/bin into every shell's PATH, and Apple has yet to explain what the directory is for.

A mystery entry appears in the PATH
A developer investigating a PATH problem has found that macOS 27.0 quietly adds a new directory, /pkg/env/global/bin, to the default shell environment on every Mac. The discovery, described in an October 18 post on anderegg.ca that reached the Hacker News front page, comes with a catch: Apple has not documented the change, and nobody appears to know yet what the directory is actually for.
According to the post's author, the first reaction to seeing an unfamiliar entry beginning with /pkg was alarm — a previously unseen root-level directory looks a lot like tampering. Only after confirming that the directory genuinely existed at the root of the filesystem did the investigation turn up the real explanation.
How the entry gets there
Since Mac OS X 10.5 shipped in 2007, the operating system has included a utility called path_helper, which builds the default PATH by reading /etc/paths and every file placed in /etc/paths.d. Most users and developers manage their own PATH additions through shell configuration files such as .zshrc instead, the author notes, and the path_helper machinery appears to be used primarily by Apple itself.
Apple has tapped this mechanism only occasionally. macOS 10.15 added a paths.d entry for the relocated rvictl utility, and macOS 13.3 added entries to support Cryptexes. macOS 27.0 continues the pattern with a new file, 10-pmk-global, which injects /pkg/env/global/bin into the PATH — except this time there is no stated purpose. The post also notes that it is unclear what the abbreviation "pmk" in the filename refers to.
A structural change to the boot volume
The /pkg directory is not just a stray folder. Citing Howard Oakley's writing on how the Mac's boot volume structure has evolved, the post explains that pkg was added to the Data volume in macOS 26.4 and only became visible at the root of the Signed System Volume with 27.0. Oakley regards this as a notable change, the post says. The directory contains four subdirectories: env, etc, inv and var.
Guesswork about its purpose
Given the name and those subdirectories, one possibility raised in the post is that /pkg could host an upcoming first-party package management system — though the author explicitly flags this as pure speculation. Apple's recent takeover of the Swift Package Index seems unrelated, the post argues, since project-level dependency management would not obviously require a directory at the root of the filesystem.
Why it matters
The immediate value of the post is diagnostic. An unexplained PATH entry pointing at a previously unseen root-level directory is exactly the kind of thing that looks like malware or a botched installation, and developers who encounter it while debugging environment problems can now rule out compromise and move on.
There is a forward-looking angle too. Because the entry is added system-wide, any executable Apple later places in /pkg/env/global/bin will be immediately resolvable in every terminal session. That makes the directory worth keeping in mind when working out which binary a command actually resolves to after a future macOS update.
Finally, the episode is a reminder that Apple still changes core system behavior without documentation. Administrators running configuration monitoring on fleets of Macs should expect this new PATH entry to appear as an unexplained diff on machines upgraded to 27.0 — and, for now at least, they will have no official explanation to attach to it.
- #macos
- #apple
- #shell
- #filesystem
- #developer-tools