Which versions of @sheltr_/agent are malicious?

The following npm versions of @sheltr_/agent are flagged malicious: 1.0.2, 1.0.4. Treat any of these as compromised.

How do I remediate @sheltr_/agent if I installed it?

@sheltr_/agent is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @sheltr_/agent — how do I know if it already compromised me?

If @sheltr_/agent 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 @sheltr_/agent part of a known attack campaign?

Yes — @sheltr_/agent is associated with the IN-MAL-2026-010286, IN-MAL-2026-015792 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 @sheltr_/agent across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @sheltr_/agent (2 malicious versions).

Malicious package

@sheltr_/agentnpm

Advisory published Jul 13, 2026Updated Aug 5, 2026

@sheltr_/agent is a confirmed malicious npm package (MAL-2026-10469) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.2, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sheltr_/agent (npm)

MAL-2026-10469

Immediate action

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

npm uninstall @sheltr_/agent

What this malware does

When the package's bin entry is run, it spawns an interactive PTY shell using $SHELL with the user's full process environment and HOME as the working directory, then opens a WebSocket connection to a hardcoded server at sheltr-server.up.railway.app. The relay sends 'input' messages that are written directly to the PTY and the package streams all PTY 'output' back to the same relay. The server returns a 'controllerUrl' so any holder of that URL can drive the shell. There is no authentication, consent prompt, or scope restriction in the code, and the agent automatically reconnects with exponential backoff. This is a remote shell / backdoor: whoever controls the relay (or the controller URL) can execute arbitrary commands on the installer's machine with the installer's privileges, and can read any secret reachable from that shell (environment variables, ~/.ssh, ~/.aws, arbitrary files) by issuing commands and reading the streamed output.

Malicious versions

2 flagged

1.0.21.0.4

Indicators of compromise (SHA-256)

0ecc4dcd6d76f100601f8b37a6b9c3aab899770ab361f2714f9193a2f8d0db78

0b4f891b36e98e7f51d4cb30fa824ef3e98d95b2d02822fef0b8549e50c2e529

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @sheltr_/agent (2 malicious versions).
If you installed it — respond
@sheltr_/agent is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @sheltr_/agent 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. @sheltr_/agent on npm has been identified as a malicious package (versions 1.0.2, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010286IN-MAL-2026-015792

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @sheltr_/agent-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database