Which versions of hex-conv-ae7a are malicious?

The following npm versions of hex-conv-ae7a are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hex-conv-ae7a if I installed it?

hex-conv-ae7a 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 hex-conv-ae7a — how do I know if it already compromised me?

If hex-conv-ae7a 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 hex-conv-ae7a part of a known attack campaign?

Yes — hex-conv-ae7a is associated with the IN-MAL-2026-007372 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 hex-conv-ae7a 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 hex-conv-ae7a (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 hex-conv-ae7a across your stack and pipelines.

Malicious package

hex-conv-ae7anpm

Malicious code in hex-conv-ae7a (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6352

Immediate action

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

npm uninstall hex-conv-ae7a

What this malware does

The package's package.json declares a postinstall hook ("postinstall": "node run.js") that runs run.js automatically on npm install. run.js imports os, fs, http, https, and child_process and collects host identity and environment data including os.hostname(), os.userInfo(), os.platform(), process.env.USER, and process.cwd(), reads files from the filesystem (fs.readFileSync, fs.existsSync), base64-encodes payloads via Buffer.from(...).toString('base64'), and POSTs the result over http/https to a remote endpoint. This is the canonical install-time host-reconnaissance and exfiltration shape: a default npm install of this package automatically sends installer machine information off-host without any user interaction or documented purpose. The package name (hex-conv with a random hex suffix) is consistent with throwaway/disposable squatting infrastructure and the package has no legitimate library functionality matching this behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

35d4f6adb1ef40a529deec65b7409b949cd93ad60d6cf3880ff5e8f0079fef1f

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 hex-conv-ae7a (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 hex-conv-ae7a across your stack and pipelines.
If you installed it — respond
hex-conv-ae7a 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 hex-conv-ae7a 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 hex-conv-ae7a 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. hex-conv-ae7a 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-007372

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hex-conv-ae7a-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