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

vv-ftend-corenpm

Malicious code in vv-ftend-core (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2429
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall vv-ftend-core

What this malware does

The package vv-ftend-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.

The OpenSSF Package Analysis project identified 'vv-ftend-core' @ 99.0.0 (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

1 flagged
99.0.0

Indicators of compromise (SHA-256)

5068b5b0eb66dc1e407d0833b7c1fb5f34b54fef2534e779d63c0cb52d227514
3096bbbc1b06c1a0df854ff812112a3d902b8a5c8926880c146f8b36e8497897
31aa4449ee3c83b67dd8e118498746b83b9b02e0d8fe6c095f6d08f6c7a9b62e

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 vv-ftend-core (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vv-ftend-core across your stack and pipelines.

  2. If you installed it — respond

    Remove vv-ftend-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 vv-ftend-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 vv-ftend-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. vv-ftend-core on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wv4c-3rwx-9p9x

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks vv-ftend-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.

vv-ftend-core (npm) malicious package — MAL-2026-2429 | O3 Security