Which versions of atlasora-sdk are malicious?

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

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

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

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

Yes — atlasora-sdk is associated with the IN-MAL-2026-007095 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-sdk 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-sdk (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-sdk across your stack and pipelines.

Malicious package

atlasora-sdknpm

atlasora-sdk is a confirmed malicious npm package (MAL-2026-6240) 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-sdk (npm)

MAL-2026-6240

Immediate action

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

npm uninstall atlasora-sdk

What this malware does

Package ships a postinstall hook (package.json scripts.postinstall: node install.js) that runs automatically on every npm install. install.js reads classic installer-secret paths — ~/.ssh/* (any file containing 'PRIVATE' or 'KEY'), ~/.aws/credentials, ~/.npmrc, and .env / .env.local / .env.production from the working directory — and bulk-scrapes 30+ environment variables shaped like credentials (PRIVATE_KEY, AWS_SECRET_ACCESS_KEY, JWT_SECRET, COINBASE_, SUPABASE_SERVICE_ROLE_KEY, ANTHROPIC_, etc.), plus host identity (os.hostname(), os.userInfo(), git config --list). The collected bundle is POSTed as JSON over HTTPS to a hardcoded anonymous webhook.site collection URL stored in a variable literally named EXFIL_SERVER. The package's index.js exports only a stub {version, name} — there is no real SDK functionality, despite the package name and description claiming to be the AtlasOra Web3 vacation-rental SDK. This is a brand-impersonation credential harvester targeting AtlasOra developers; any machine that runs npm install atlasora-sdk is fully compromised.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

cc75492c0a0ce4090918bfdef0cea9cc028ef4c8273283d32085189e13a59c51

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-sdk (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-sdk across your stack and pipelines.
If you installed it — respond
atlasora-sdk 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-sdk 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-sdk 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-sdk 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-007095

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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