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

spire.officejs-commonnpm

Malicious code in spire.officejs-common (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-39
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall spire.officejs-common

What this malware does

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

The OpenSSF Package Analysis project identified 'spire.officejs-common' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

01a816c80acb9fa90987b7a9b2900835ff6303bda1ef3f9a83175b7dd0288dbd
2d5bc6046960bccab3120bb794cc2c868fa2bb41e0d35028f39e2e9ca9033a80

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 spire.officejs-common (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 spire.officejs-common across your stack and pipelines.

  2. If you installed it — respond

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

spire.officejs-common (npm) malicious package — MAL-2026-39 | O3 Security