Which versions of tempo-components are malicious?

The following npm versions of tempo-components are flagged malicious: 99.0.1. Treat any of these as compromised.

How do I remediate tempo-components if I installed it?

tempo-components is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed tempo-components — how do I know if it already compromised me?

If tempo-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.

Is tempo-components part of a known attack campaign?

Yes — tempo-components is associated with the IN-MAL-2026-004682, IN-MAL-2026-004683 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find tempo-components across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tempo-components (version 99.0.1).

Malicious package

tempo-componentsnpm

Advisory published May 25, 2026Updated May 26, 2026

tempo-components is a confirmed malicious npm package (MAL-2026-4685) that steals credentials and exfiltrates sensitive data (malicious version 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tempo-components (npm)

MAL-2026-4685

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall tempo-components

What this malware does

The package contains a file (poc.js) that imports os, https, fs, and child_process; collects host identifiers including os.hostname(), os.platform(), and the output of whoami; and POSTs the data via https.request to an external endpoint. This is a classic system-reconnaissance and exfiltration shape with no benign interpretation for a package distributed under a 'components' name. Installing or loading this code on a build or developer machine causes host metadata and identity information to be transmitted off-host.

Malicious versions

1 flagged

99.0.1

Indicators of compromise (SHA-256)

6790e6e83af71238b9773ae49568f5374d094d23d1a7247ef4560d645ef64024

9f516fddd52133764a3ff124d5ec3f47b7327e7f6df709614b6040dc4eb35b3c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for tempo-components (version 99.0.1).
If you installed it — respond
tempo-components is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tempo-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. tempo-components on npm has been identified as a malicious package (version 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004682IN-MAL-2026-004683

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tempo-components-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database