MAL-2026-17169 Malicious code in @alphaspace/core (npm)
Malicious package
Published
MAL-2026-17169 is a malicious package: @alphaspace/core (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-17169/ (Markdown: https://insights.sbomify.com/MAL-2026-17169/index.md)
- Package
- @alphaspace/core
- Registry
- npm
What is MAL-2026-17169?
MAL-2026-17169 is a malicious package in @alphaspace/core, published on 25 Sep 2026.
Official description
preinstall.js runs unconditionally on npm install and POSTs a JSON payload to a hardcoded Pipedream collector at https://f5778d1d81cc30c39dcdd0da5ca1d49a.m.pipedream.net. The payload includes os.hostname(), os.userInfo() username, platform/arch/node version, process.env.INIT_CWD, process.cwd(), the consumer project's package.json name and version, whether the consumer declares an @alphaspace dependency, npm registry hosts parsed from ~/.npmrc, CI-related environment variable names, and proxy host configuration. The same script performs DNS resolution against a hardcoded list of *.yahoo.com and .ouryahoo.com internal hostnames (including istio-system.prod1-gq1.omega.yahoo.com and buildr.corp.yahoo.com), and for any banana.stand..yahoo.com name that resolves it issues an https.request with rejectUnauthorized:false, capturing the response status, Server header, and first 512 bytes of the body and forwarding them in a banana_proof field of the exfil payload. The @alphaspace scope name and an in-file 'authorized security research' banner form a dependency-confusion lure aimed at Yahoo internal builds; the installer-side behavior — host fingerprinting, npmrc/registry disclosure, and TLS-verification-disabled internal-network probing from the installer's host — fires against any machine that resolves this package.
What should I do about MAL-2026-17169?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.