Which versions of narrow-array are malicious?

The following npm versions of narrow-array are flagged malicious: 4.8.2, 4.8.3. Treat any of these as compromised.

How do I remediate narrow-array if I installed it?

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

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

Yes — narrow-array is associated with the GHSA-6cq7-pjjx-42h3, RLMA-2026-01441 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 narrow-array 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 narrow-array (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging narrow-array across your stack and pipelines.

Malicious package

narrow-arraynpm

Malicious code in narrow-array (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-827

Immediate action

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

npm uninstall narrow-array

What this malware does

The package narrow-array was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

4.8.24.8.3

Indicators of compromise (SHA-256)

8bbee1a11c9aa9d6feb751063161f9802c6245890a9764cdddf190d3357df462

508eafee6916ba29ade3caf0722e7bffe693e53fa35a4e74f0dc385950778f34

ef138207af0e7943306814acfed8bf5fe6d0f852711f7d95e8264d3fb11182a0

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 narrow-array (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging narrow-array across your stack and pipelines.
If you installed it — respond
Remove narrow-array 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 narrow-array 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 narrow-array 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. narrow-array on npm has been identified as a malicious package (versions 4.8.2, 4.8.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6cq7-pjjx-42h3RLMA-2026-01441

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks narrow-array-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