Which versions of @shared-runtime/modules are malicious?

The following npm versions of @shared-runtime/modules are flagged malicious: 9.9.10. Treat any of these as compromised.

How do I remediate @shared-runtime/modules if I installed it?

Remove @shared-runtime/modules 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 @shared-runtime/modules — how do I know if it already compromised me?

If @shared-runtime/modules 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 @shared-runtime/modules part of a known attack campaign?

Yes — @shared-runtime/modules is associated with the IN-MAL-2026-020187 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 @shared-runtime/modules across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @shared-runtime/modules (version 9.9.10).

Malicious package

@shared-runtime/modulesnpm

Advisory published Sep 18, 2026Updated Sep 18, 2026

@shared-runtime/modules is a confirmed malicious npm package (MAL-2026-16291) that executes malicious code on install (malicious version 9.9.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @shared-runtime/modules (npm)

MAL-2026-16291

Immediate action

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

npm uninstall @shared-runtime/modules

What this malware does

@shared-runtime/[email protected] collects the installer's OS username (os.userInfo().username), hostname (os.hostname()) and current working-directory basename, then issues a dns.resolve4() query against a subdomain assembled as srmods.<user>.<host>.<cwd>.<ts>.oob.algamil7x.xyz, leaking those values via authoritative DNS logs at the attacker-controlled domain oob.algamil7x.xyz. The destination hostname, the OS/DNS API names, and the module names are stored as hex byte arrays in lib/a74d1f.js and lib/f63c0e.js and reconstructed at runtime via String.fromCharCode, with os and dns loaded through module.constructor._load to avoid literal require() strings. Execution is triggered both at install (package.json scripts.install="node index.js") and on require() (index.js top-level require('./lib/core.js')), with a swallowed try/catch so npm install still reports success. The README claims no hidden network calls in module scope while module scope performs exactly that.

Malicious versions

1 flagged

9.9.10

Indicators of compromise (SHA-256)

bc6095cf4766c948193c22d8c0e775010fc3ab47733a1020fb8fd5367d88e5e9

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-020187

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @shared-runtime/modules-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