MAL-2026-18286: Malicious code in @ppa-web-components/ppa-navigation (npm)

Published Oct 25, 2026
·
Updated

@ppa-web-components/ppa-navigation is a dependency-confusion package: it is described as a "Compatibility shim", uses inflated version numbers, and its README calls it an "authorized dependency-confusion test". Each listed version (1.0.1, 1.0.0, 2.0.0, 99.0.1, 3.0.0, 2.0.1) has a postinstall script that runs node beacon.cjs on npm install, and index.js calls the same code when the package is imported; it POSTs the hostname, install path and current working directory over plain HTTP to http://185.158.107.175:8787/ah/dc, and index.js exports a Proxy that returns no-op functions so builds importing the real package keep running. The npm account wiseke published 14 such packages under the @greenlake, @sxm-web, @drone-js-ext and @ppa-web-components scopes between 2026-10-23 21:23 and 2026-10-25 14:28 UTC; index.js is byte-identical to that of ph-common (MAL-2026-1809), which sends to the same endpoint.

--- -= Per source details. Do not edit below this line.=-

Source: amazon-inspector (c88c344e72bb7cf5ae6f5e6185a1024caf8b96bce96584d448609ab78cd894af) The package is a shim whose only functional payload is a beacon. package.json declares a postinstall that runs node beacon.cjs, and index.js additionally invokes require('./beacon.cjs').fire() on load, so the beacon fires both at npm install and whenever any consumer requires the package. The beacon POSTs the installer's hostname, install path, current working directory, and Node version to the hardcoded bare-IP plain-HTTP endpoint http://185.158.107.175:8787/ah/dc. The destination is not a registry, not a documented first-party service, and the plain-IP + non-standard port shape is inconsistent with any legitimate vendor telemetry. The package otherwise exports a Proxy that returns no-op functions for every property and self-describes as a 'Compatibility shim', so the beacon is the entire payload. The scoped name @ppa-web-components/ppa-navigation has the shape of a dependency-confusion or typosquat probe against an internal @ppa-web-components namespace.

Source: ghsa-malware (b810a6b75e53293eb696e1672c7bbb4c9681eb89895bfc8d080aa527575070e5) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Affected Software

1 affected component
npm/@ppa-web-components/ppa-navigation*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove @ppa-web-components/ppa-navigation from your environment.

    Remove the package from affected computers.

  2. Operational

    Immediately rotate all secrets and keys stored on any affected computer, performing the rotation from a different computer.

Event History

Oct 25, 2026
Advisory Published
via OSV·02:19 PM
Data Sourced
via OSV·02:19 PM
DescriptionAffected Software

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203