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

vv-ftend-apinpm

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

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

What this malware does

The package vv-ftend-api 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-api' @ 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)

64929518f767cb6362b2d269ab86fafd0ff115be566c5c2fe8eed474b1cab905
52e6dc460495b044b5104f5b43ce39cacbc3bddfd089ca9f48ba821fb9d9b77c
516291f1a77610b9273279b0bfc4b6502c42024be5ce84308ad96ab226fa216d

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-api (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-api across your stack and pipelines.

  2. If you installed it — respond

    Remove vv-ftend-api 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-api 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-api 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-api 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-xprf-4c78-3wc4

References

Credits

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

Detect & block this

O3 blocks vv-ftend-api-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-api (npm) malicious package — MAL-2026-2428 | O3 Security