Which versions of node-intend are malicious?

The following npm versions of node-intend are flagged malicious: 3.3.5. Treat any of these as compromised.

How do I remediate node-intend if I installed it?

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

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

Yes — node-intend is associated with the RLMA-2026-01461 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 node-intend across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for node-intend (version 3.3.5).

Malicious package

node-intendnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

node-intend is a confirmed malicious npm package (MAL-2026-1803) that executes malicious code on install (malicious version 3.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-intend (npm)

MAL-2026-1803

Immediate action

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

npm uninstall node-intend

What this malware does

The package node-intend was found to contain malicious code.

Malicious versions

1 flagged

3.3.5

Indicators of compromise (SHA-256)

a67db39cf5d10670bce028081c5b4c1efff735eb2a2795985e5d68f104219140

ba5f9e681ba9ecd6ac8399dc29bec6a699bd3595529aaebb037a7a0f79204746

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01461

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks node-intend-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