GHAPPIER Hijacks npm Trusted Publishing to Distribute Malicious Package, Researchers Find

Security researchers have uncovered that a threat group identified as GHAPPIER leveraged npm's Trusted Publishing mechanism to push a malicious package into the public registry, raising fresh concerns about software supply‑chain integrity.

The Trusted Publishing feature, introduced by npm to verify that code originates from an authorized maintainer, attaches a cryptographic provenance record to each release. In theory, this allows downstream projects to trust that a package has not been tampered with after the original author signs it.

According to a report from CloudSEK, the GHAPPIER actors managed to compromise a legitimate npm package that already carried a valid trusted‑publishing provenance tag. By inserting malicious payloads into the compromised version, they were able to distribute harmful code while preserving the appearance of authenticity, making detection by automated tools more difficult.

While the exact capabilities of the injected code have not been fully disclosed, analysts note that typical supply‑chain payloads can harvest environment variables, exfiltrate credentials, or execute arbitrary commands on a victim's build system. Because the package appeared to be signed by a trusted source, developers who incorporated it into their projects were unlikely to suspect foul play.

The incident adds to a growing list of high‑profile supply‑chain attacks that have targeted open‑source ecosystems, from the SolarWinds breach to the recent event‑streaming library compromise. As more organizations rely on third‑party JavaScript components, the attack surface expands, and any weakness in provenance verification can be weaponized.

npm officials responded by revoking the compromised version and urging maintainers to review their publishing credentials. They also announced plans to tighten verification checks and improve monitoring for anomalous provenance patterns. Security experts advise developers to adopt a layered defense: pin specific package versions, employ integrity‑checking tools, and regularly audit dependencies for unexpected changes.