Which versions of atlasora-shared are malicious?

The following npm versions of atlasora-shared are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate atlasora-shared if I installed it?

atlasora-shared 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 atlasora-shared — how do I know if it already compromised me?

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

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

Malicious package

atlasora-sharednpm

atlasora-shared is a confirmed malicious npm package (MAL-2026-6241) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in atlasora-shared (npm)

MAL-2026-6241

Immediate action

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

npm uninstall atlasora-shared

What this malware does

package.json declares "postinstall": "node install.js", causing install.js to run automatically on npm install. install.js requires https, fs, os, and child_process, collects host identifiers via os.hostname() and os.userInfo(), executes shell commands via execSync(...), probes filesystem paths with fs.existsSync(...), and POSTs the collected data to a remote endpoint via https.request(...). This is the canonical install-time system-information exfiltration pattern: identifying data is gathered from the installer's machine and beaconed outbound on every install, with no documented purpose tied to the package's stated function. Installing this package automatically leaks host and user information to an external destination.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e1bd49976f774ef8357d29c74bc366b851e69a611cc5894f1a59621d91f9daba

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

Campaign

IN-MAL-2026-007099

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks atlasora-shared-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