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

@tt-aem-tt4a/shared-componentsnpm

Advisory published Updated

@tt-aem-tt4a/shared-components is a confirmed malicious npm package (MAL-2026-5639) that executes malicious code on install (malicious version 10.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @tt-aem-tt4a/shared-components (npm)

MAL-2026-5639
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @tt-aem-tt4a/shared-components

What this malware does

The OpenSSF Package Analysis project identified '@tt-aem-tt4a/shared-components' @ 10.0.0 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
10.0.0

Indicators of compromise (SHA-256)

817c1920ad6f83b25d8fd32b77999376a6ad3b5448e93e7b0b66cce72ec4dac0

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @tt-aem-tt4a/shared-components (version 10.0.0).

  2. If you installed it — respond

    Remove @tt-aem-tt4a/shared-components 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 @tt-aem-tt4a/shared-components 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. @tt-aem-tt4a/shared-components on npm has been identified as a malicious package (version 10.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @tt-aem-tt4a/shared-components-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

@tt-aem-tt4a/shared-components (npm) malicious package — MAL-2026-5639 | O3 Security