Which versions of @quantixfinance/tron are malicious?

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

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

@quantixfinance/tron 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/tron — how do I know if it already compromised me?

If @quantixfinance/tron 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/tron part of a known attack campaign?

Yes — @quantixfinance/tron is associated with the IN-MAL-2026-019372 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/tron 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/tron (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/tron across your stack and pipelines.

Malicious package

@quantixfinance/tronnpm

@quantixfinance/tron is a confirmed malicious npm package (MAL-2026-15855) 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/tron (npm)

MAL-2026-15855

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @quantixfinance/tron

What this malware does

The package's declared preinstall script iterates process.env, filters keys against a broad credential/secret keyword list (key, secret, token, pass, private, mnemonic, seed, api, wallet, tron, rpc, infura, alchemy, database, supabase, vercel, railway, and similar), attaches hostname, cwd, and node version, and POSTs the collected JSON to a hardcoded IPv4 host encoded as the integer literal 759017974 (45.61.177.246) on port 61289 with a random-hex path. Numeric-integer encoding of the destination hides the address from string/URL scanners. The shipped index.js is a two-line no-op stub and the README does not mention any network activity, so the package's only material behavior on npm install is credential harvesting.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

dcf106f622a8d60232e7d296737eab7e44ffc42a598f40b4b2afea24aaa15f7c

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/tron (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/tron across your stack and pipelines.
If you installed it — respond
@quantixfinance/tron 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/tron 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/tron 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/tron 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-019372

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @quantixfinance/tron-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