Which versions of atlasora-utils are malicious?

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

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

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

Yes — atlasora-utils is associated with the IN-MAL-2026-007096 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-utils 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-utils and packages like it before any post-install script runs.

Malicious package

atlasora-utilsnpm

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

MAL-2026-6243

Immediate action

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

npm uninstall atlasora-utils

What this malware does

On npm install, the package's postinstall hook (node install.js, declared in package.json) harvests secrets from the installer's machine and POSTs them to a hardcoded attacker-controlled webhook at https://webhook.site/22e20640-e2a1-4bb2-b203-061077d055ff. Collected data includes: a long list of named environment variables (COINBASE_*, OPENAI_API_KEY, AWS_ACCESS_KEY_ID/SECRET, JWT_SECRET, PRIVATE_KEY, MNEMONIC, etc.); the contents of .env, .env.local, and .env.production from the current working directory and parent directories; files under ~/.ssh/ filtered for content containing PRIVATE or KEY (private SSH keys); ~/.aws/credentials; ~/.npmrc (npm auth tokens); and the output of git config --list. The source uses a constant explicitly named EXFIL_SERVER and labels the operation as a collection target. The package also masquerades as an internal AtlasOra package — the console output prints @atlasora/shared: installed successfully while the actual package name is atlasora-utils, consistent with a dependency-confusion lure targeting developers of the AtlasOra project.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

cf7c54cd0923afe13aadf778a5c213363c521e7a50c4b9e235bf6c7cf58a973d

Frequently asked questions

No. atlasora-utils 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-007096

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