Which versions of azurestack-common are malicious?

The following npm versions of azurestack-common are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate azurestack-common if I installed it?

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

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

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

Search your lockfiles and build artifacts for azurestack-common (2 malicious versions).

Malicious package

azurestack-commonnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

azurestack-common is a confirmed malicious npm package (MAL-2026-2335) that executes malicious code on install (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in azurestack-common (npm)

MAL-2026-2335

Immediate action

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

npm uninstall azurestack-common

What this malware does

The package azurestack-common was found to contain malicious code.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

789843607dcf3852cf649e1c9eb6bd474749ecb653a97205a8f142a710946424

500acb5021d6cc7c40146b6b6f8fd17563f17b68d95e52d78a749514b839cba3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01712

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks azurestack-common-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