Which versions of @navify-platform/auth are malicious?

The following npm versions of @navify-platform/auth are flagged malicious: 3.7.0. Treat any of these as compromised.

How do I remediate @navify-platform/auth if I installed it?

Remove @navify-platform/auth from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @navify-platform/auth — how do I know if it already compromised me?

If @navify-platform/auth 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 @navify-platform/auth part of a known attack campaign?

Yes — @navify-platform/auth is associated with the RLMA-2025-04851 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 @navify-platform/auth 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 @navify-platform/auth (version 3.7.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @navify-platform/auth across your stack and pipelines.

Part of a larger attack: @navify-platform published 8 malicious packages. See the full campaign →

Malicious package

@navify-platform/authnpm

@navify-platform/auth is a confirmed malicious npm package (MAL-2025-41354) that executes malicious code on install (malicious version 3.7.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @navify-platform/auth (npm)

MAL-2025-41354

Immediate action

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

npm uninstall @navify-platform/auth

What this malware does

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

3.7.0

Indicators of compromise (SHA-256)

1f134e8203183c5039c94e657a5e2196b56163ab7c51fb7fb1945cbc9c428a40

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @navify-platform/auth (version 3.7.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @navify-platform/auth across your stack and pipelines.
If you installed it — respond
Remove @navify-platform/auth from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @navify-platform/auth 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 @navify-platform/auth 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. @navify-platform/auth on npm has been identified as a malicious package (version 3.7.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04851

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @navify-platform/auth-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

Explore

All malware advisories How O3 detects malware Vulnerability database