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

@navancorp/ta-fe-componentsnpm

@navancorp/ta-fe-components is a confirmed malicious npm package (MAL-2025-47041) that executes malicious code on install (malicious versions 1.0.1, 1.0.3, 1.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @navancorp/ta-fe-components (npm)

MAL-2025-47041
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @navancorp/ta-fe-components

What this malware does

The package @navancorp/ta-fe-components 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

8 flagged
1.0.11.0.31.0.41.0.51.0.71.0.81.0.91.2.9213

Indicators of compromise (SHA-256)

ea9ac90aa6a85cd2ff704d7ebf6928a5015a78c68b643de047583737e115a088
2b03a6280002a6a847b1903673d7bf71df9afe3c314b05e06010368ac6dd3654
48ce27a677ba360356260cc72cb40cbfa72c370f08f3bd8047ee2c78890b9290
48079d004a85a26495bd9aa127894421095c5cf0182acf915d81fc9b0eac57b5

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 @navancorp/ta-fe-components (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @navancorp/ta-fe-components across your stack and pipelines.

  2. If you installed it — respond

    Remove @navancorp/ta-fe-components 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 @navancorp/ta-fe-components 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 @navancorp/ta-fe-components 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. @navancorp/ta-fe-components on npm has been identified as a malicious package (versions 1.0.1, 1.0.3, 1.0.4, 1.0.5, 1.0.7, 1.0.8, 1.0.9, 1.2.9213 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4fjr-q2c3-8832RLMA-2025-04850RLUA-2026-01037

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @navancorp/ta-fe-components-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.

Explore

@navancorp/ta-fe-components (npm) malicious package — MAL-2025-47041 | O3 Security