Which versions of @quantixfinance/api are malicious?

The following npm versions of @quantixfinance/api are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @quantixfinance/api if I installed it?

@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.

I already installed @quantixfinance/api — how do I know if it already compromised me?

If @quantixfinance/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.

Is @quantixfinance/api part of a known attack campaign?

Yes — @quantixfinance/api is associated with the IN-MAL-2026-019364 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @quantixfinance/api across my projects, lockfiles, and CI pipelines?

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

Malicious package

@quantixfinance/apinpm

@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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @quantixfinance/api (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @quantixfinance/api across your stack and pipelines.
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.
Did it already run?
If @quantixfinance/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.
How O3 protects you
O3 blocks @quantixfinance/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. @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

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database