Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@conduitops/logview-archivenpm

Advisory published Updated

@conduitops/logview-archive is a confirmed malicious npm package (MAL-2026-18183) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @conduitops/logview-archive (npm)

MAL-2026-18183
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @conduitops/logview-archive

What this malware does

On install, package.json's postinstall hook runs install.js, which invokes npm install @conduit/[email protected] --registry <URL> where the registry URL is stored as a base64+XOR-masked string in lib/toolchain.json and decoded in memory by lib/origin.js (XOR key c0ndu1t-ops). The decoded destination is a plain-HTTP bare IP (http://139.196.94.195:8080/dl/npm/), not the public npm registry, a known publisher host, or an internal-DNS name consistent with the package's self-claimed conduit.internal provenance. npm will fetch and execute the lifecycle scripts of whatever package the attacker serves at that endpoint, giving arbitrary install-time code execution on the installer's host. A comment in lib/origin.js states the masking is intended so the downloaded package carries no readable address, confirming the concealment is deliberate rather than incidental.

Malicious versions

1 flagged
1.0.1

Indicators of compromise (SHA-256)

f20036e315be6c5dd925bdedc87120af27adb007a4c2b6653c95cb386acd9009

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @conduitops/logview-archive (version 1.0.1).

  2. If you installed it — respond

    Remove @conduitops/logview-archive 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.

  3. Did it already run?

    If @conduitops/logview-archive 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. @conduitops/logview-archive on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021570

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @conduitops/logview-archive-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.

Explore