Which versions of @shared-web/assets are malicious?

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

How do I remediate @shared-web/assets if I installed it?

@shared-web/assets is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @shared-web/assets — how do I know if it already compromised me?

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

Yes — @shared-web/assets is associated with the IN-MAL-2026-020181 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-web/assets 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 @shared-web/assets (version 9.9.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @shared-web/assets across your stack and pipelines.

Malicious package

@shared-web/assetsnpm

@shared-web/assets is a confirmed malicious npm package (MAL-2026-16283) that steals credentials and exfiltrates sensitive data (malicious version 9.9.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @shared-web/assets (npm)

MAL-2026-16283

Immediate action

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

npm uninstall @shared-web/assets

What this malware does

The package runs an install lifecycle script (node index.js) and also executes ./lib/core.js on require. That code collects os.userInfo().username, os.hostname(), and process.cwd() and issues a DNS resolve4 for a label chain of the form <pkg>.<user>.<host>.<cwd>.<ts>.oob.algamil7x.xyz, exfiltrating installer identity and working-directory information over DNS to an attacker-controlled domain. The destination host and the os/dns/process module names are obfuscated in lib/c5df9a.js and lib/b4ce8f.js using char-code byte arrays (String.fromCharCode) and loaded via module.constructor._load instead of plain require, concealing both the APIs and the C2 destination. The obfuscation and DNS-label-encoded channel are inconsistent with the package's presentation as a shared web assets helper.

Malicious versions

1 flagged

9.9.10

Indicators of compromise (SHA-256)

e8fd9342e97dc9f655a994fe1091125f717cbfa7b89aa6a2333662ad23ad6771

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @shared-web/assets (version 9.9.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @shared-web/assets across your stack and pipelines.
If you installed it — respond
@shared-web/assets is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @shared-web/assets 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 @shared-web/assets 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. @shared-web/assets 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-020181

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @shared-web/assets-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database