Which versions of js-soul are malicious?

The following npm versions of js-soul are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate js-soul if I installed it?

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

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

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

Search your lockfiles and build artifacts for js-soul (version 1.0.4).

Malicious package

js-soulnpm

Advisory published Aug 25, 2026Updated Aug 25, 2026

js-soul is a confirmed malicious npm package (MAL-2026-14477) that executes malicious code on install (malicious version 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in js-soul (npm)

MAL-2026-14477

Immediate action

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

npm uninstall js-soul

What this malware does

On module load, src/api/session-api.js reads../../../../public/logo.ico (a path outside the package), DES-decrypts the contents with the hardcoded key 'bf497c0b9cee', spawns a detached node child process via child_process.spawn with {detached:true}, and pipes the decrypted plaintext into the interpreter's stdin, executing arbitrary code at import 'js-soul'. The disguise of executable JavaScript as an image asset, the hardcoded DES key, and an unrelated 'ThetaSDK initialization error' catch-block string contradict the package's stated purpose as a session helper library and its README claim that nothing runs on import. Any code the attacker stages at the sibling path executes in the installer process with the installer's privileges.

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

3e5bb2e2d2011a8e8bcc3c0fba8aeed7cca1e1b92e19ea867535a27dbf2cc500

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-018694

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks js-soul-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