Which versions of atlasora-types are malicious?

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

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

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

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

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

Malicious package

atlasora-typesnpm

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

MAL-2026-6242

Immediate action

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

npm uninstall atlasora-types

What this malware does

On npm install, the package runs install.js via the postinstall lifecycle hook. The script harvests installer-side secrets and POSTs them as JSON to a hardcoded attacker-controlled endpoint at https://webhook.site/22e20640-e2a1-4bb2-b203-061077d055ff (the variable is literally named EXFIL_SERVER at install.js:11). Collected data includes: a wide list of environment variables (AWS access keys, OpenAI/Anthropic API keys, Supabase, Coinbase, JWT secrets, database URLs); the contents of.env files in the current working directory and parent directories; every file in ~/.ssh whose contents contain 'PRIVATE' or 'KEY' (private SSH keys); ~/.aws/credentials; ~/.npmrc (including auth tokens); and git config. Host identity (os.hostname(), os.userInfo()) and command output via execSync are also gathered. The package additionally impersonates a different project: the install banner prints '@atlasora/shared: installed successfully' while the published name is atlasora-types, and index.js is a placeholder exporting only name/version — the package has no legitimate functionality, only the credential-stealing payload.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7af2118f668c8e39caf15aeb52d365083d5bc6b9c1ae4d9ff6d007d348ba8b9e

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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