Which versions of @alphaspace/core are malicious?

The following npm versions of @alphaspace/core are flagged malicious: 99.0.0, 99.0.1, 99.0.2. Treat any of these as compromised.

How do I remediate @alphaspace/core if I installed it?

@alphaspace/core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @alphaspace/core — how do I know if it already compromised me?

If @alphaspace/core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @alphaspace/core part of a known attack campaign?

Yes — @alphaspace/core is associated with the IN-MAL-2026-020551, IN-MAL-2026-020550, IN-MAL-2026-020543 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @alphaspace/core across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @alphaspace/core (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @alphaspace/core across your stack and pipelines.

Malicious package

@alphaspace/corenpm

@alphaspace/core is a confirmed malicious npm package (MAL-2026-17169) that steals credentials and exfiltrates sensitive data (malicious versions 99.0.0, 99.0.1, 99.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @alphaspace/core (npm)

MAL-2026-17169

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @alphaspace/core

What this malware does

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.

Malicious versions

3 flagged

99.0.099.0.199.0.2

Indicators of compromise (SHA-256)

0ab2a5d4024e6452d72efe9470634b7bf9fc3dbb0bd4d49d571138f777a81864

0c7bcaf9dd8835f994b72bc50cf41ef1194429600fef3d271b99f32305ebd726

42d10ba1427af01794dfb0a6b39a05f969547455e9d86d75f18601b1d035c507

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @alphaspace/core (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @alphaspace/core across your stack and pipelines.
If you installed it — respond
@alphaspace/core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @alphaspace/core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @alphaspace/core before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @alphaspace/core on npm has been identified as a malicious package (versions 99.0.0, 99.0.1, 99.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020551IN-MAL-2026-020550IN-MAL-2026-020543

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @alphaspace/core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database