Which versions of optimizely-starter-kit-for-fastly-compute are malicious?

The following npm versions of optimizely-starter-kit-for-fastly-compute are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate optimizely-starter-kit-for-fastly-compute if I installed it?

optimizely-starter-kit-for-fastly-compute 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 optimizely-starter-kit-for-fastly-compute — how do I know if it already compromised me?

If optimizely-starter-kit-for-fastly-compute 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 optimizely-starter-kit-for-fastly-compute part of a known attack campaign?

Yes — optimizely-starter-kit-for-fastly-compute is associated with the IN-MAL-2026-018174 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 optimizely-starter-kit-for-fastly-compute 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 optimizely-starter-kit-for-fastly-compute (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging optimizely-starter-kit-for-fastly-compute across your stack and pipelines.

Malicious package

optimizely-starter-kit-for-fastly-computenpm

optimizely-starter-kit-for-fastly-compute is a confirmed malicious npm package (MAL-2026-14138) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in optimizely-starter-kit-for-fastly-compute (npm)

MAL-2026-14138

Immediate action

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

npm uninstall optimizely-starter-kit-for-fastly-compute

What this malware does

package.json declares preinstall: node index.js, causing index.js to run automatically on npm install. The script collects host identifiers (os.hostname(), os.userInfo(), homedir, DNS servers, __dirname, package.json contents) and reads /etc/passwd and /etc/hosts, then POSTs the payload over HTTPS to aguu8c8gjyt4anjao3nhru1mgdm5avyk.oastify.com, a Burp Collaborator out-of-band interaction subdomain. The package name resembles legitimate Optimizely/Fastly Compute tooling, consistent with a dependency-confusion or typosquat exfiltration beacon.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

72b7bcd65cbf07a90130de5e4a29fb72bc99badb287a1e1dc7373c288a1ae0be

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 optimizely-starter-kit-for-fastly-compute (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging optimizely-starter-kit-for-fastly-compute across your stack and pipelines.
If you installed it — respond
optimizely-starter-kit-for-fastly-compute 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 optimizely-starter-kit-for-fastly-compute 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 optimizely-starter-kit-for-fastly-compute 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. optimizely-starter-kit-for-fastly-compute on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018174

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks optimizely-starter-kit-for-fastly-compute-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