Which versions of spire.officejs-externs are malicious?

Every published version of spire.officejs-externs on npm is considered malicious. Remove the package entirely.

How do I remediate spire.officejs-externs if I installed it?

Remove spire.officejs-externs 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.

I already installed spire.officejs-externs — how do I know if it already compromised me?

If spire.officejs-externs was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find spire.officejs-externs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spire.officejs-externs (all published versions).

Malicious package

spire.officejs-externsnpm

Advisory published Jan 16, 2026Updated Jan 16, 2026

spire.officejs-externs is a confirmed malicious npm package (MAL-2026-312) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spire.officejs-externs (npm)

MAL-2026-312

Immediate action

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

npm uninstall spire.officejs-externs

What this malware does

The package spire.officejs-externs was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

9dfb46e06f3d17c765d605a42471cb4f6b75133ef12587b0dd769276a77fddcc

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for spire.officejs-externs (all published versions).
If you installed it — respond
Remove spire.officejs-externs 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.
Did it already run?
If spire.officejs-externs was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. spire.officejs-externs on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks spire.officejs-externs-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database