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

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

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

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

If @finaxis/common-js 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.

Is @finaxis/common-js part of a known attack campaign?

Yes — @finaxis/common-js is associated with the IN-MAL-2026-017968, IN-MAL-2026-018266, IN-MAL-2026-018268, IN-MAL-2026-018267, IN-MAL-2026-018265 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?

Search your lockfiles and build artifacts for @finaxis/common-js (5 malicious versions).

Malicious package

@finaxis/common-jsnpm

Advisory published Aug 15, 2026Updated Aug 19, 2026

@finaxis/common-js is a confirmed malicious npm package (MAL-2026-14064) that steals credentials and exfiltrates sensitive data (malicious versions 0.3.4, 0.3.5, 0.3.6…). 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 publishes under a lodash-imitating identity: keywords lodash/lodash-js, and the README is a verbatim copy of the official lodash 4.18.1 README. The single shipped file dist/common-js.js is not lodash — it is a ~770 KB javascript-obfuscator bundle (17,969-entry rotated string array, _0xNNNN identifiers). After deobfuscation the bundle is a browser-based cryptocurrency-mining client: it opens a WebSocket to a caller/config-supplied pool URL, spawns a fan-out of Web Workers keyed by workerId, handles nonce framing, and bundles an AES-GCM decryption primitive (aesGcmDecrypt from @noble/ciphers) for pool message decryption. Wallet and worker identifiers are read from a config object with fallbacks (cfg.wallet||'x', cfg.worker||'worker'). A developer who installs this expecting a lodash-family utility and ships it in a web application will silently mine cryptocurrency on their end users' browsers, consuming visitor CPU/battery and creating a compliance/abuse liability for the downstream site. The identity masquerade (name/keywords/README all mimicking lodash) combined with heavy string-array obfuscation of the real payload is the standard shape of a supply-chain masquerade attack.

Malicious versions

5 flagged

0.3.40.3.50.3.60.3.80.3.10

Indicators of compromise (SHA-256)

f708a31239d3dc7490906a4a41f5ccb3cb76c99f89bc87b5ad5884939bb2d308

d3a81522907c6036250cd04caf2b6350ad1903fd50ed138cda550ec33a1a7ea0

832d1ce61ce1f1e1430c60e94175cc80700dfbb2f8d0f46fd7d00b64720026d8

858e186e40af34fa05e49209b9bfeb758f4b734da30dacd6bd66cdb5c77a368b

c6fdee952074aa29c57bde30ce12f536868aba1a38faf68a861d856e21cd7f36

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @finaxis/common-js (5 malicious versions).
If you installed it — respond
@finaxis/common-js 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 @finaxis/common-js 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. @finaxis/common-js on npm has been identified as a malicious package (versions 0.3.4, 0.3.5, 0.3.6, 0.3.8, 0.3.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017968IN-MAL-2026-018266IN-MAL-2026-018268IN-MAL-2026-018267IN-MAL-2026-018265

References

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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database