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

@velora-dex/sdknpm

Malicious code in @velora-dex/sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2510
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @velora-dex/sdk

What this malware does

Malicious npm package executing base64-decoded shell command to download and run stage-2 payload from C2 server (89.36.224.5) targeting macOS

The package @velora-dex/sdk was found to contain malicious code.

The OpenSSF Package Analysis project identified '@velora-dex/sdk' @ 9.4.1 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
9.4.1

Indicators of compromise (SHA-256)

21a732dd2745098176d2c19fe3edb359db6f6690b5d14b8d49e8a00b61325311
013b2c71633a40b8d425f998bb589074e403eea3069a0af42d70a041827475a3

Detection & response playbook

Backdoor / remote access

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @velora-dex/sdk (version 9.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @velora-dex/sdk across your stack and pipelines.

  2. If you installed it — respond

    @velora-dex/sdk establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If @velora-dex/sdk 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 @velora-dex/sdk 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. @velora-dex/sdk on npm has been identified as a malicious package (version 9.4.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

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

Detect & block this

O3 blocks @velora-dex/sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring