Which versions of log-res are malicious?

The following npm versions of log-res are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate log-res if I installed it?

Remove log-res 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 log-res — how do I know if it already compromised me?

If log-res 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 log-res part of a known attack campaign?

Yes — log-res is associated with the IN-MAL-2026-018407 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 log-res across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for log-res (version 1.0.3).

Malicious package

log-resnpm

Advisory published Aug 19, 2026Updated Aug 19, 2026

log-res is a confirmed malicious npm package (MAL-2026-14292) that executes malicious code on install (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in log-res (npm)

MAL-2026-14292

Immediate action

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

npm uninstall log-res

What this malware does

index.js re-exports a desKey string sourced from apps/docs/app/theta.js, which reads apps/docs/app/des.db as UTF-8. des.db contains a heavily obfuscated JavaScript program (string-array + hex-name mangling) that, when evaluated, creates a directory under the OS temp directory, writes a synthetic package.json declaring runtime dependencies on axios, better-sqlite3, node-machine-id, and socket.io-client, spawns npm install inside that directory, and then spawns node on a staged index.js. The payload is disguised as a database file (des.db) rather than shipped as source, and the stager fetches and runs a socket.io-client-based remote agent capable of receiving commands from an attacker-controlled endpoint. The package's advertised purpose (a docs/monorepo TheData API helper) does not require embedding or exporting an obfuscated executable blob.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

59f23ea1c6c40021fb69210eba68cdbda94b42f4e255f78758778b90ebb09d78

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for log-res (version 1.0.3).
If you installed it — respond
Remove log-res 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 log-res 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. log-res on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018407

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks log-res-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