Which versions of utif-updated are malicious?

The following npm versions of utif-updated are flagged malicious: 99.0.1, 99.0.3, 99.0.4. Treat any of these as compromised.

How do I remediate utif-updated if I installed it?

Remove utif-updated 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.

I already installed utif-updated — how do I know if it already compromised me?

If utif-updated was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is utif-updated part of a known attack campaign?

Yes — utif-updated is associated with the GHSA-j9gx-q4v7-8gh6 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 utif-updated across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for utif-updated (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging utif-updated across your stack and pipelines.

Malicious package

utif-updatednpm

Malicious code in utif-updated (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192688

Immediate action

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

npm uninstall utif-updated

What this malware does

The package utif-updated was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'utif-updated' @ 99.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

99.0.199.0.399.0.4

Indicators of compromise (SHA-256)

c956a798985ddee3a3f9e6292a9dc8d68491dfa39608f44ed787403970a261eb

ab7225cae4978e140af4a4cb470911ab6c99c619023f0bd0f54d3f9610ec145d

e2dfe76e7e3dfc47d48cabb35526119dec20df52ff648f3f5d110f91f0a7ad1b

24ed42240868e0b6b0eff870ffa0f42d95bca3659f922078257f1a71694da3f1

3d854467203e61d8d828eafa2a699ba639c90e4045f0e92f033fdade35096cac

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for utif-updated (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging utif-updated across your stack and pipelines.
If you installed it — respond
Remove utif-updated 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.
Did it already run?
If utif-updated was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks utif-updated before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. utif-updated on npm has been identified as a malicious package (versions 99.0.1, 99.0.3, 99.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j9gx-q4v7-8gh6

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks utif-updated-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.

Malware detection Runtime egress monitoring