Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @quantixfinance published 10 malicious packages. See the full campaign →
Malicious package

@quantixfinance/apinpm

Advisory published Updated

@quantixfinance/api is a confirmed malicious npm package (MAL-2026-15848) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @quantixfinance/api (npm)

MAL-2026-15848
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @quantixfinance/api

What this malware does

The package's preinstall lifecycle script runs automatically on npm install. It iterates process.env and collects every variable whose name contains credential-shaped substrings (key, secret, token, pass, mnemonic, seed, private, wallet, rpc, infura, alchemy, supabase, vercel, railway, api, env, url, database, contract, tron, deploy), along with hostname, cwd, and Node version, and POSTs the JSON payload via http.request to a hardcoded destination whose hostname is encoded as the bare integer 759017974 (decoding to IP 45.55.109.86) on port 61289, under a long random path. Errors are silently swallowed. The advertised main entry index.js is a stub exporting empty get/post/put/delete no-ops, so the manifest plus preinstall is the entire payload; the package presents as an API client while its only real behavior is install-time credential theft.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

574ee760d08ba89b3c9a06d87af077eac7166d12ed8a98b00a30298c0236b6e7

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @quantixfinance/api (version 1.0.0).

  2. If you installed it — respond

    @quantixfinance/api is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @quantixfinance/api was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @quantixfinance/api on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019364

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @quantixfinance/api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@quantixfinance/api (npm) malicious package — MAL-2026-15848 | O3 Security