MalwarePublished 29 Jun 2026Updated 14 Aug 2026

@epic-common/observability-node (npm) · Malicious Code

Affects @epic-common/observability-nodeSource GCVE Database

Malicious package : remove @epic-common/observability-node and rotate any secrets on hosts that installed it.

Data as of 26 Oct 2026, 15:55 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6562

What to do

Remove @epic-common/observability-node from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@epic-common/observability-node	Affected 0.0.1 – 10.10.2 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package @epic-common/observability-node versions 10.10.1 and 10.10.2 contains malicious code that exfiltrates environment variable names and metadata, as well as credential fingerprints, to an external endpoint. It masquerades as a legitimate OpenTelemetry API re-export to avoid detection. This results in unauthorized disclosure of sensitive environment information and credential-related data from the host machine.

Impact

Sensitive environment variables and host identifiers are exfiltrated to a non-first-party external endpoint, potentially exposing credential metadata and enabling offline attacks to recover secrets. This compromises confidentiality of environment secrets and host information on any machine that installs or builds with the affected package versions from the public npm registry.

Defensive guidance

Users should avoid installing or importing @epic-common/observability-node versions 10.10.1 and 10.10.2 from the public npm registry. Instead, ensure that package resolution is strictly from trusted internal registries. Monitor dependencies for unauthorized or unexpected packages from the @epic-common scope. Since this is a malicious package masquerading as a legitimate dependency, removing the package and rebuilding environments is recommended.

Summary

The @epic-common/observability-node package, published under the Epic Games private scope but available on the public npm registry, acts as a dependency confusion attack vector. When importing the ./api subpath, it enumerates all environment variable keys and sends them along with host details (hostname, current working directory, platform, architecture) to a remote URL. For environment variables matching credential-like patterns (e.g., TOKEN, SECRET, PASSWORD, AWS, GCP, etc.), it transmits the variable name, value length, first two characters, and SHA-256 hash of the value. This enables offline brute-force or dictionary attacks against low-entropy secrets. The package re-exports the genuine OpenTelemetry API to appear legitimate, causing builds to succeed while silently leaking sensitive data. This behavior occurs if the package is resolved from the public npm registry instead of an internal Epic Games registry, exposing build or install environments to data exfiltration without consent.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Jun 2026, 22:41 UTC

Technical details

References

Community reviews