Which versions of test-dev-host are malicious?

The following npm versions of test-dev-host are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate test-dev-host if I installed it?

test-dev-host 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 test-dev-host — how do I know if it already compromised me?

If test-dev-host 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 test-dev-host part of a known attack campaign?

Yes — test-dev-host is associated with the GHSA-6v46-5v2x-c3c5, IN-MAL-2026-010987 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 test-dev-host 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 test-dev-host (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-dev-host across your stack and pipelines.

Malicious package

test-dev-hostnpm

test-dev-host is a confirmed malicious npm package (MAL-2026-11491) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-dev-host (npm)

MAL-2026-11491

Immediate action

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

npm uninstall test-dev-host

What this malware does

[email protected] connects out to a hardcoded socket server (host/port sourced from the test-dev-config module) and enters a receive-loop that dispatches remote messages to handlers for 'command', 'download', 'upload', 'archive', 'install', 'grabext', 'keylog', and 'address'. This gives the remote operator arbitrary shell command execution, file read/write, archive exfiltration, and browser-extension install/theft on the installer's host. On a 'keylog' message the agent flushes a keystroke buffer, computes a hardware fingerprint, and uploads the local keylog file via uploadFileToPublicApi keyed by machineId. src/py_launcher.js also fetches XOR+base64-encrypted (key 'w3x') address replacements from ${DJANGO_API_URL}/address and installs them as helper.wallet_replacements, implementing the clipboard/wallet-address swap pattern that redirects cryptocurrency transfers to attacker-controlled addresses. Obfuscation (base64 + XOR of C2-supplied data) is used to conceal the wallet-swap payload.

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

0.1.0

Indicators of compromise (SHA-256)

27cded0e4f6f17de980e65abefd0ed8b4a24a7f817e8a8506492d4ed87d5ab82

85b3df759cd11b9c662bed5840b0671d4e9c54a76a606d284ca39390ecf51f8d

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 test-dev-host (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-dev-host across your stack and pipelines.
If you installed it — respond
test-dev-host 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 test-dev-host 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 test-dev-host 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. test-dev-host on npm has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6v46-5v2x-c3c5IN-MAL-2026-010987

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks test-dev-host-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