Which versions of @tt-aem-tt4a/shared-components are malicious?

The following npm versions of @tt-aem-tt4a/shared-components are flagged malicious: 10.0.0. Treat any of these as compromised.

How do I remediate @tt-aem-tt4a/shared-components if I installed it?

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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Can O3 Security detect @tt-aem-tt4a/shared-components in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @tt-aem-tt4a/shared-components and packages like it before any post-install script runs.

Malicious package

@tt-aem-tt4a/shared-componentsnpm

Malicious code in @tt-aem-tt4a/shared-components (npm) Remove it immediately and rotate any exposed credentials.

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

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

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection