Which versions of tempo-modules are malicious?

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

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

tempo-modules 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-modules — how do I know if it already compromised me?

If tempo-modules 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-modules part of a known attack campaign?

Yes — tempo-modules is associated with the IN-MAL-2026-004688, IN-MAL-2026-004690 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-modules across my projects, lockfiles, and CI pipelines?

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

Malicious package

tempo-modulesnpm

Advisory published May 25, 2026Updated May 26, 2026

tempo-modules is a confirmed malicious npm package (MAL-2026-4687) 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-modules (npm)

MAL-2026-4687

Immediate action

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

npm uninstall tempo-modules

What this malware does

[email protected] is a dependency-confusion attack package. The package.json preinstall hook executes poc.js, which on every npm install harvests hostname, username, full network configuration (ipconfig/ip a/resolv.conf), git remote, parent package.json, and CI pipeline definitions (.gitlab-ci.yml,.github/workflows, Jenkinsfile, azure-pipelines.yml), plus whoami/id output. It then iterates process.env and selects any key containing TOKEN, AWS, AZURE, NPM, GITHUB, GITLAB, CI, JENKINS, BUILD, WALMART, etc. — bulk credential scraping of cloud and CI tokens. The collected JSON is POSTed to https://d8a5d9pon5bugoc35cngp9hcregcqyezu.oast.me/<pkg> (an Interactsh out-of-band collector), with a hex-encoded host-user identifier additionally DNS-exfiltrated. The package is published at version 99.0.1 with an internal-sounding name to win dependency-confusion resolution against an organization's private registry; the description self-identifies as a 'Dependency Confusion PoC' for a bug-bounty program, but the published artifact harms any installer that resolves this name. Multiple independent block signals stack: lifecycle preinstall outbound exfil, bulk credential harvest of CI/cloud tokens, and dependency-confusion version inflation.

Malicious versions

1 flagged

99.0.1

Indicators of compromise (SHA-256)

6ad4276e2eafbe6d7040f94ac546ec20e7ac211e1e5906964c25f581a519d183

7fe7b908b9ebd546f11dc133ed56c3eb783c144f258be19e3e9e9a81770f09b2

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for tempo-modules (version 99.0.1).
If you installed it — respond
tempo-modules 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-modules 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-modules 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-004688IN-MAL-2026-004690

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tempo-modules-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