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?

Remove atlasora-types 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

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.

Can O3 Security detect atlasora-types in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking atlasora-types and packages like it before any post-install script runs.

Malicious package

atlasora-typesnpm

Malicious code in atlasora-types (npm) Remove it immediately and rotate any exposed credentials.

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

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

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection