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?

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

If atlasora-utils 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-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.

How do I find atlasora-utils 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-utils (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-utils across your stack and pipelines.

Malicious package

atlasora-utilsnpm

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

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

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

Detect & block this

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