Which versions of nordpass are malicious?

The following npm versions of nordpass are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate nordpass if I installed it?

nordpass is a typosquat — you almost certainly intended a legitimately-named package. Remove nordpass, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed nordpass — how do I know if it already compromised me?

If nordpass 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 nordpass part of a known attack campaign?

Yes — nordpass is associated with the IN-MAL-2026-010741 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 nordpass 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 nordpass (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 nordpass across your stack and pipelines.

Malicious package

nordpassnpm

Malicious code in nordpass (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10743

Immediate action

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

npm uninstall nordpass

What this malware does

Package name impersonates the NordPass password-manager product while presenting itself as 'A simple authentication module.' The package.json postinstall runs make -C src && cp src/auth_module./bin/flare && node src/install.js. src/install.js is a ~100 KB heavily obfuscated file (obfuscator.io-style string-array decoder with rotation, unicode-escaped identifiers, XOR-numeric literals) that reads /etc/passwd, derives XOR key material from that content combined with hardcoded byte constants, base64-decodes an embedded payload, XOR-decrypts it, and passes the resulting string to eval(). The decode-and-exec path is guarded by anti-analysis checks: a NODE_OPTIONS --inspect check, a Date.now() timing gate, and an OG_-prefixed environment-variable kill switch. A compiled auth_module binary is also staged to ./bin/flare during postinstall. The combination — brand impersonation, obfuscation, host-file read used as key material, base64+XOR+eval of an embedded blob, anti-debug and kill-switch guards, and a staged native binary — executes attacker-controlled code on the installer's machine at npm install time.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

9df6f21fababcd99ba522d380a0729d35aa4ff44ee2f6612fe75b906da844aee

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nordpass (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 nordpass across your stack and pipelines.
If you installed it — respond
nordpass is a typosquat — you almost certainly intended a legitimately-named package. Remove nordpass, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If nordpass 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 nordpass 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. nordpass 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-010741

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nordpass-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring