Which versions of sjs-builders are malicious?

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

How do I remediate sjs-builders if I installed it?

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

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

Yes — sjs-builders is associated with the GHSA-55q4-68jc-wrgw 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 sjs-builders across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sjs-builders (version 1.0.4).

Malicious package

sjs-buildersnpm

Advisory published Jul 6, 2026Updated Jul 6, 2026

sjs-builders is a confirmed malicious npm package (MAL-2026-6877) 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 sjs-builders (npm)

MAL-2026-6877

Immediate action

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

npm uninstall sjs-builders

What this malware does

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

1.0.4

Indicators of compromise (SHA-256)

33403134956efdf214a788395f07fbe72b53f2403770f4674554a0c53cd35468

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sjs-builders (version 1.0.4).
If you installed it — respond
Remove sjs-builders 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 sjs-builders 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. sjs-builders 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

GHSA-55q4-68jc-wrgw

References

github.com

Detect & block this

O3 blocks sjs-builders-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