NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

ostk-otel-autoconfignpm

Advisory published Updated

ostk-otel-autoconfig is a confirmed malicious npm package (MAL-2026-511) that executes malicious code on install (malicious versions 2.4.4, 2.4.5, 2.7.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ostk-otel-autoconfig (npm)

MAL-2026-511
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ostk-otel-autoconfig

What this malware does

The package ostk-otel-autoconfig 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 'ostk-otel-autoconfig' @ 2.4.4 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

3 flagged
2.4.42.4.52.7.1

Indicators of compromise (SHA-256)

b6c6da346f0373ebad97994067d5f50c763b278ab5f70c4f372586222aea2735
eda252bb6f91619b02f1e9c7b7584c9dd50e219e46afc2763df7a085a368b8a0
2523cd47e1801a33b2f2bda82fadc530646d1eb6c9fdd4eaf07f67d577c06bd7
42d5f49a4cdcc1502660b6c0a3a8f62e1dd94de3408e1b16e9f0e6a41266c4d0
5b222e0d41ae144cf784f7fd2c40bd0c9bcb213c76581f4f9285f6f5d3baf36a

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for ostk-otel-autoconfig (3 malicious versions).

  2. If you installed it — respond

    Remove ostk-otel-autoconfig 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 ostk-otel-autoconfig 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. ostk-otel-autoconfig on npm has been identified as a malicious package (versions 2.4.4, 2.4.5, 2.7.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wcfp-f27x-6p4p

References

Credits

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

Detect & block this

O3 blocks ostk-otel-autoconfig-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.

Explore

ostk-otel-autoconfig (npm) malicious package — MAL-2026-511 | O3 Security