Which versions of nextiva-dot-com are malicious?

The following npm versions of nextiva-dot-com are flagged malicious: 1.1.2. Treat any of these as compromised.

How do I remediate nextiva-dot-com if I installed it?

Remove nextiva-dot-com 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 nextiva-dot-com — how do I know if it already compromised me?

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

Yes — nextiva-dot-com is associated with the RLMA-2026-01448 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 nextiva-dot-com across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nextiva-dot-com (version 1.1.2).

Malicious package

nextiva-dot-comnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

nextiva-dot-com is a confirmed malicious npm package (MAL-2026-1797) that executes malicious code on install (malicious version 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nextiva-dot-com (npm)

MAL-2026-1797

Immediate action

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

npm uninstall nextiva-dot-com

What this malware does

The package nextiva-dot-com was found to contain malicious code.

Malicious versions

1 flagged

1.1.2

Indicators of compromise (SHA-256)

42d080b1141d124db43cbb18343247f42160f445442411abab5d6b7ac03df2c3

b526416f0bec682e1493700f926a23b44ef0517c358700e8a9b0025028363f0c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nextiva-dot-com (version 1.1.2).
If you installed it — respond
Remove nextiva-dot-com 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 nextiva-dot-com 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. nextiva-dot-com on npm has been identified as a malicious package (version 1.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01448

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks nextiva-dot-com-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