Which versions of @finaxis/common-js are malicious?

The following npm versions of @finaxis/common-js are flagged malicious: 0.3.4. Treat any of these as compromised.

How do I remediate @finaxis/common-js if I installed it?

@finaxis/common-js hijacks resources to mine cryptocurrency. Remove it, check for abnormal CPU/GPU and cloud-cost spikes, and rotate any credentials exposed to the compromised process.

I already installed @finaxis/common-js — how do I know if it already compromised me?

If @finaxis/common-js 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 @finaxis/common-js part of a known attack campaign?

Yes — @finaxis/common-js is associated with the IN-MAL-2026-017968 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 @finaxis/common-js 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 @finaxis/common-js (version 0.3.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @finaxis/common-js across your stack and pipelines.

Malicious package

@finaxis/common-jsnpm

@finaxis/common-js is a confirmed malicious npm package (MAL-2026-14064) that hijacks the host to mine cryptocurrency (malicious version 0.3.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @finaxis/common-js (npm)

MAL-2026-14064

Immediate action

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

npm uninstall @finaxis/common-js

What this malware does

Package is published with a README copied from lodash v4.18.1 and keywords ['lodash','lodash-js'], but the sole shipped module dist/common-js.js is a heavily obfuscated bundle (javascript-obfuscator with string-array rotation and hex-named identifiers, produced by the package's own scripts.obfuscate build step) implementing a Xelis (XEL) proof-of-work miner. The bundle contains a stratum protocol client (stratum:// URLs, mining.ping, mining.set_extranonce, mining.hashrate), a Web Worker mining loop (mineBatch, HASH_BATCH), and an embedded ~46KB base64 WASM payload exporting wasm_xelis_hash_v3 and wasm_mine_batch. Nothing in the shipped code implements a lodash-compatible utility API. Consumers that install this thinking they are getting lodash instead load a covert cryptominer that consumes the host's CPU/GPU on behalf of the attacker's Xelis mining pool.

Malicious versions

1 flagged

0.3.4

Indicators of compromise (SHA-256)

f708a31239d3dc7490906a4a41f5ccb3cb76c99f89bc87b5ad5884939bb2d308

Detection & response playbook

Cryptominer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @finaxis/common-js (version 0.3.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @finaxis/common-js across your stack and pipelines.
If you installed it — respond
@finaxis/common-js hijacks resources to mine cryptocurrency. Remove it, check for abnormal CPU/GPU and cloud-cost spikes, and rotate any credentials exposed to the compromised process.
Did it already run?
If @finaxis/common-js 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 @finaxis/common-js 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. @finaxis/common-js on npm has been identified as a malicious package (version 0.3.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017968

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @finaxis/common-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the mining traffic and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database