Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

stacks-editornpm

Malicious code in stacks-editor (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2629
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall stacks-editor

What this malware does

The package stacks-editor was found to contain malicious code.

The OpenSSF Package Analysis project identified 'stacks-editor' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

1a6ea6b9be40bdfc9059c0960297c393a8314a45445dd8fcd42ced99521cee4d
15f50509d5d9110a7233db4ed683100cc33c07a09055d93d32ed8f057a34ae3f

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove stacks-editor from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If stacks-editor 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.

  4. How O3 protects you

    O3 blocks stacks-editor 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. stacks-editor on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks stacks-editor-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

stacks-editor (npm) malicious package — MAL-2026-2629 | O3 Security