Which versions of node-stack-frames are malicious?

The following npm versions of node-stack-frames are flagged malicious: 4.0.0. Treat any of these as compromised.

How do I remediate node-stack-frames if I installed it?

node-stack-frames 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 node-stack-frames — how do I know if it already compromised me?

If node-stack-frames 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 node-stack-frames part of a known attack campaign?

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

Malicious package

node-stack-framesnpm

node-stack-frames is a confirmed malicious npm package (MAL-2026-5736) that steals credentials and exfiltrates sensitive data (malicious version 4.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-stack-frames (npm)

MAL-2026-5736

Immediate action

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

npm uninstall node-stack-frames

What this malware does

package.json declares a preinstall script that runs an inline Node program on npm install. The script requires os and http, collects os.hostname(), os.platform(), and os.arch(), base64-encodes the result, and issues an HTTP GET to https://d8lslmi9io6i264ftj80mh9e7niqiaenf.oast.live/?data=<encoded>. The host is a Project Discovery interactsh (OAST) subdomain used as an out-of-band collection endpoint. The package ships no functional code — its own description identifies it as a security holding placeholder — so the only effect of installing it is the automatic exfiltration of installer host identifiers to an attacker-controlled collector. This matches a dependency-confusion / recon beacon pattern.

Malicious versions

1 flagged

4.0.0

Indicators of compromise (SHA-256)

5fd4f6c5f3278484d99f6ffffc001cf920dcb0fa4fdfabff957a61c3cfbfc158

eb14f033b6997244fdd890fbfacba9c82a164fd26a201cc39ee76408d70f208e

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

Campaign

IN-MAL-2026-006317IN-MAL-2026-006318

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks node-stack-frames-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