Which versions of tensor-fi-crypto-utils are malicious?

The following npm versions of tensor-fi-crypto-utils are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate tensor-fi-crypto-utils if I installed it?

Remove tensor-fi-crypto-utils 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 tensor-fi-crypto-utils — how do I know if it already compromised me?

If tensor-fi-crypto-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 tensor-fi-crypto-utils part of a known attack campaign?

Yes — tensor-fi-crypto-utils is associated with the RLMA-2025-05963 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 tensor-fi-crypto-utils across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tensor-fi-crypto-utils (version 1.0.0).

Malicious package

tensor-fi-crypto-utilsnpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

tensor-fi-crypto-utils is a confirmed malicious npm package (MAL-2025-191597) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tensor-fi-crypto-utils (npm)

MAL-2025-191597

Immediate action

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

npm uninstall tensor-fi-crypto-utils

What this malware does

The package tensor-fi-crypto-utils was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ab2f7c6973a364150020d9afb3bba24655aa9c52e49d945a00bff11e6c50bc27

e9ed8cc30500616c36f3301bfeb5ec377ea53456fdfcbcb8fa1993346cb64958

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tensor-fi-crypto-utils (version 1.0.0).
If you installed it — respond
Remove tensor-fi-crypto-utils 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 tensor-fi-crypto-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. tensor-fi-crypto-utils on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05963

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks tensor-fi-crypto-utils-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

Explore

All malware advisories How O3 detects malware Vulnerability database