Which versions of @temptation.js/utils are malicious?

The following npm versions of @temptation.js/utils are flagged malicious: 999.9.15, 999.9.16. Treat any of these as compromised.

How do I remediate @temptation.js/utils if I installed it?

@temptation.js/utils 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 @temptation.js/utils — how do I know if it already compromised me?

If @temptation.js/utils 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 @temptation.js/utils part of a known attack campaign?

Yes — @temptation.js/utils is associated with the IN-MAL-2026-018627, IN-MAL-2026-018631 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 @temptation.js/utils across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @temptation.js/utils (2 malicious versions).

Malicious package

@temptation.js/utilsnpm

Advisory published Aug 24, 2026Updated Aug 24, 2026

@temptation.js/utils is a confirmed malicious npm package (MAL-2026-14410) that steals credentials and exfiltrates sensitive data (malicious versions 999.9.15, 999.9.16). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @temptation.js/utils (npm)

MAL-2026-14410

Immediate action

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

npm uninstall @temptation.js/utils

What this malware does

The package registers a preinstall hook (node index.js) that runs on npm install and harvests installer-side data: os.hostname(), OS username, home directory, local IPv4, public IP resolved via https://api.ipify.org / https://icanhazip.com / https://ifconfig.me, DNS resolver info, INIT_CWD, parent project package.json fields, CI context (GitHub Actions/GitLab/Jenkins/Azure DevOps repo, actor, run id), AWS_REGION, npm registry URL, git user.email domain, and the output of gh api user --jq.login and npm whoami — using the installer's authenticated gh/npm CLI sessions to attribute the install to a real developer account. The collected JSON is hex-encoded, split into 60-character chunks, and exfiltrated via DNS resolutions of the form <i>-<hex>.u-<uuid>.da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun (an OAST/interactsh callback host) as well as HTTPS/HTTP POSTs to /poc/<uuid> at the same host. A source comment describes the DNS channel as designed to survive corporate egress filtering. The version number 999.9.15 is a dependency-confusion overshoot intended to win private-name resolution against an internal package of the same name.

The OpenSSF Package Analysis project identified '@temptation.js/utils' @ 999.9.16 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

999.9.15999.9.16

Indicators of compromise (SHA-256)

c8d0cfc44fc0fd8c597831c7da133a0e02ba0f1644f9777edb7629099bb367b8

b729ceb1ad2301a684d94c580ee75c4d6b352fd05061b84076e959975645777b

3b8ac41747a5c926627c28c9f1a651df91cd3447b07ca4cafabc1916004d1e70

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @temptation.js/utils (2 malicious versions).
If you installed it — respond
@temptation.js/utils 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 @temptation.js/utils 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. @temptation.js/utils on npm has been identified as a malicious package (versions 999.9.15, 999.9.16 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018627IN-MAL-2026-018631

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @temptation.js/utils-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