Which versions of @nxt-costco-com/forge-components are malicious?

The following npm versions of @nxt-costco-com/forge-components are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate @nxt-costco-com/forge-components if I installed it?

Remove @nxt-costco-com/forge-components 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 @nxt-costco-com/forge-components — how do I know if it already compromised me?

If @nxt-costco-com/forge-components 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 @nxt-costco-com/forge-components part of a known attack campaign?

Yes — @nxt-costco-com/forge-components is associated with the RLMA-2026-01039 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 @nxt-costco-com/forge-components across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @nxt-costco-com/forge-components (version 9.9.9).

Malicious package

@nxt-costco-com/forge-componentsnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

@nxt-costco-com/forge-components is a confirmed malicious npm package (MAL-2026-1631) that executes malicious code on install (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nxt-costco-com/forge-components (npm)

MAL-2026-1631

Immediate action

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

npm uninstall @nxt-costco-com/forge-components

What this malware does

The package @nxt-costco-com/forge-components was found to contain malicious code.

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

6c0dd0240bae460664f41d30ba27863e40233fdda210e495c520e7480ed840e5

4a0e0f35823f6346841117866bac7213bfac75a55af137f2e63b2ac33dba9a54

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01039

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @nxt-costco-com/forge-components-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