Which versions of aligned-array are malicious?

The following npm versions of aligned-array are flagged malicious: 3.4.3, 3.4.4. Treat any of these as compromised.

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

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

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

Yes — aligned-array is associated with the GHSA-j7qj-j3fg-5xc8, RLMA-2026-01103 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 aligned-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 aligned-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 aligned-array across your stack and pipelines.

Malicious package

aligned-arraynpm

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

MAL-2026-670

Immediate action

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

npm uninstall aligned-array

What this malware does

The package aligned-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

3.4.33.4.4

Indicators of compromise (SHA-256)

ea83ead9b32cbe9a0c64af15ea5b84c39dad6ba94e7688ec712ceb8d1b2e8185

f2e1b553bdbf785a336d224d5d3594c204455937469510cdbc423519287b2360

6d7965d5052187a958fa54f90dbe0183745e325e31688cb4b149f55fc8bd9bcd

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 aligned-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 aligned-array across your stack and pipelines.
If you installed it — respond
Remove aligned-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 aligned-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 aligned-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. aligned-array on npm has been identified as a malicious package (versions 3.4.3, 3.4.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j7qj-j3fg-5xc8RLMA-2026-01103

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks aligned-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