What does the @hoteldev/common malware do?

build/index.js appends an eval(atob(...)) block after the normal __exportStar section that decodes to an import-time loader. The loader resolves a C2 IP by reading an Ethereum transaction associated with wallet 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a (via eth_getBlockByNumber), then issues HTTP requests to http:// :443/0x/cls and http:// :443/0x/ls with an x-payload-b64 header, XOR-decrypts the responses, and launches each decoded body through spawn('node', ['-e', ], {detached: true, stdio: 'ignore', windowsHide: true}).unref(). Strings inside the payload (http, https, spawn, child_process, eth_getBlockByNumber, x-payload-b64) are written as \u#### unicode e

Which versions of @hoteldev/common are malicious?

The following npm versions of @hoteldev/common are flagged malicious: 1.0.9. Treat any of these as compromised.

How do I remediate @hoteldev/common if I installed it?

@hoteldev/common 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 @hoteldev/common — how do I know if it already compromised me?

If @hoteldev/common was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @hoteldev/common part of a known attack campaign?

Yes — @hoteldev/common is associated with the IN-MAL-2026-014709, GHSA-62r9-p944-cjmg 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 @hoteldev/common across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @hoteldev/common (version 1.0.9).

Malicious package

@hoteldev/commonnpm

Advisory published Aug 5, 2026Updated Aug 6, 2026

@hoteldev/common is a confirmed malicious npm package (MAL-2026-12318) that steals credentials and exfiltrates sensitive data (malicious version 1.0.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @hoteldev/common (npm)

MAL-2026-12318

Immediate action

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

npm uninstall @hoteldev/common

What this malware does

build/index.js appends an eval(atob(...)) block after the normal __exportStar section that decodes to an import-time loader. The loader resolves a C2 IP by reading an Ethereum transaction associated with wallet 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a (via eth_getBlockByNumber), then issues HTTP requests to http://<derived-IP>:443/0x/cls and http://<derived-IP>:443/0x/ls with an x-payload-b64 header, XOR-decrypts the responses, and launches each decoded body through spawn('node', ['-e', <payload>], {detached: true, stdio: 'ignore', windowsHide: true}).unref(). Strings inside the payload (http, https, spawn, child_process, eth_getBlockByNumber, x-payload-b64) are written as \u#### unicode escapes to hide the behavior from casual review. The loader runs on any require/import of the package, giving the operator of the on-chain-designated host arbitrary, hidden, detached code execution on the installer's machine, with the C2 address rotatable via a new Ethereum transaction.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.9

Indicators of compromise (SHA-256)

9bb27849cbb16840b019ef47d6a84627d61eb9d48df28da5a9bc1a208e1ff758

aacfc893117769583694bc71a02db63d49b37b36243c48e00fa492c68e6beb37

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @hoteldev/common (version 1.0.9).
If you installed it — respond
@hoteldev/common 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 @hoteldev/common was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @hoteldev/common on npm has been identified as a malicious package (version 1.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014709GHSA-62r9-p944-cjmg

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @hoteldev/common-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