Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

tensor-fi-utils-corenpm

Malicious code in tensor-fi-utils-core (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192375
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tensor-fi-utils-core

What this malware does

The package tensor-fi-utils-core 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.

Malicious versions

6 flagged
1.0.01.0.11.0.21.0.41.1.01.3.0

Indicators of compromise (SHA-256)

b899d0f59ef690b315a4961f681ad6c7cc81af32cb33772406f675064184ee66
097848a520bc6a7316c011e97b306f4743b5498acdeccea54d5d4a0ab44bdebd
a8bbb4b2174573f7449ac7f23722c0a75a423df275f3b4746300762844288c83
1f7552933727ae23ca62abf9a1651d10051b9e5c88db5864829bb4bb1d7626a8

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove tensor-fi-utils-core 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.

  3. Did it already run?

    If tensor-fi-utils-core 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.

  4. How O3 protects you

    O3 blocks tensor-fi-utils-core 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. tensor-fi-utils-core on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.4, 1.1.0, 1.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hjxg-jf6x-5vqpRLMA-2025-06514RLUA-2026-01611

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

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

tensor-fi-utils-core (npm) malicious package — MAL-2025-192375 | O3 Security