Which versions of @wizloft/harness-context are malicious?

The following npm versions of @wizloft/harness-context are flagged malicious: 0.1.1-alpha.3. Treat any of these as compromised.

How do I remediate @wizloft/harness-context if I installed it?

Remove @wizloft/harness-context 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 activity or persistence.

I already installed @wizloft/harness-context — how do I know if it already compromised me?

If @wizloft/harness-context 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 @wizloft/harness-context part of a known attack campaign?

Yes — @wizloft/harness-context is associated with the IN-MAL-2026-018408 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 @wizloft/harness-context 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 @wizloft/harness-context (version 0.1.1-alpha.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wizloft/harness-context across your stack and pipelines.

Malicious package

@wizloft/harness-contextnpm

@wizloft/harness-context is a confirmed malicious npm package (MAL-2026-14286) that executes malicious code on install (malicious version 0.1.1-alpha.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @wizloft/harness-context (npm)

MAL-2026-14286

Immediate action

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

npm uninstall @wizloft/harness-context

What this malware does

dist/index.js (the package's declared main) contains a heavily obfuscated obfuscator.io-style IIFE appended after the legitimate context-service code. On import, the payload stashes global.r = require and global.m = module, then issues HTTPS requests to an Ethereum public RPC endpoint (h.drpc.org) and a block-explorer account API to read state from contract 0xa322E5f3..., using that state to resolve a next-stage URL that is fetched and executed in-process. The obfuscated string array (~303 entries via a rotated decoder) hides drpc.org, ?module=ac, POST, application/json, Mozilla/5., and the contract address. This is the EtherHiding loader pattern: attacker-controlled contract state serves as a mutable pointer to arbitrary code executed in the installer/consumer process at require time. Behavior does not match the package's advertised purpose of a small typed capability contract.

Malicious versions

1 flagged

0.1.1-alpha.3

Indicators of compromise (SHA-256)

b0315deb3fb6b42e929a55eafaeaedbf1b428ee8873d4ae31f5ec9956f21b554

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @wizloft/harness-context (version 0.1.1-alpha.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wizloft/harness-context across your stack and pipelines.
If you installed it — respond
Remove @wizloft/harness-context 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 activity or persistence.
Did it already run?
If @wizloft/harness-context 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 @wizloft/harness-context 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. @wizloft/harness-context on npm has been identified as a malicious package (version 0.1.1-alpha.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018408

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wizloft/harness-context-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database