Which versions of shelf-jwt-sessions are malicious?

The following npm versions of shelf-jwt-sessions are flagged malicious: 0.1.2. Treat any of these as compromised.

How do I remediate shelf-jwt-sessions if I installed it?

shelf-jwt-sessions 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 shelf-jwt-sessions — how do I know if it already compromised me?

If shelf-jwt-sessions was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is shelf-jwt-sessions part of a known attack campaign?

Yes — shelf-jwt-sessions is associated with the RLMA-2025-06481 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 shelf-jwt-sessions across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for shelf-jwt-sessions (version 0.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shelf-jwt-sessions across your stack and pipelines.

Malicious package

shelf-jwt-sessionsnpm

Malicious code in shelf-jwt-sessions (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191423

Immediate action

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

npm uninstall shelf-jwt-sessions

What this malware does

The package shelf-jwt-sessions was found to contain malicious code.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.1.2

Indicators of compromise (SHA-256)

fade5707bac9f21e7be73df0a6be3e1a960f547e30930a244f551062bc276993

bccf31522a4305a972564f73554c2b148fd28428cce67b3e73edd235aec25a84

a43b76be10970d81063441d48f24044a3c691217fabf2d8ea6d7fd61cc2aece3

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for shelf-jwt-sessions (version 0.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shelf-jwt-sessions across your stack and pipelines.
If you installed it — respond
shelf-jwt-sessions 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 shelf-jwt-sessions was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks shelf-jwt-sessions before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. shelf-jwt-sessions on npm has been identified as a malicious package (version 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06481

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks shelf-jwt-sessions-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