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

overstock-health-expressnpm

Malicious code in overstock-health-express (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-514
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall overstock-health-express

What this malware does

The package overstock-health-express was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'overstock-health-express' @ 1.4.5 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

4 flagged
1.4.41.4.51.6.11.6.2

Indicators of compromise (SHA-256)

35d0330177ea7cff9d44e4258f3988e07cad91176be792a270fd419090cbbbe1
0127dbf155b313c81fad7d9e7c1bf4c4e7c4697831612d4c5e0e6b6f3e6ee083
3e34a94f75d061d1d406a741138056223baaad7939a781a62409268980462127
dcfc6b693e8bc612e6aeacfc8ea8dad81c100e61ccd3a36777603404f14875a5
ed3e7577b619bd126b6e79b6a32538ec0928c941c3386e7ac0faf7bac66f78a6
88927f419aeeb8999fb1b8be70403f14230ba9189e1bde2179b717f55c8c3217

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 overstock-health-express (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging overstock-health-express across your stack and pipelines.

  2. If you installed it — respond

    Remove overstock-health-express 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 overstock-health-express 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 overstock-health-express 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. overstock-health-express on npm has been identified as a malicious package (versions 1.4.4, 1.4.5, 1.6.1, 1.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8689-38pm-xg5f

References

Credits

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

Detect & block this

O3 blocks overstock-health-express-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.

overstock-health-express (npm) malicious package — MAL-2026-514 | O3 Security