Which versions of shinhan-limit-scrap are malicious?

The following npm versions of shinhan-limit-scrap are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate shinhan-limit-scrap if I installed it?

shinhan-limit-scrap 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 shinhan-limit-scrap — how do I know if it already compromised me?

If shinhan-limit-scrap 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 shinhan-limit-scrap part of a known attack campaign?

Yes — shinhan-limit-scrap is associated with the GHSA-p92h-9qvq-2vq2 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 shinhan-limit-scrap 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 shinhan-limit-scrap (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shinhan-limit-scrap across your stack and pipelines.

Malicious package

shinhan-limit-scrapnpm

Malicious code in shinhan-limit-scrap (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190782

Immediate action

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

npm uninstall shinhan-limit-scrap

What this malware does

The package shinhan-limit-scrap was found to contain malicious code.

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.

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.

The OpenSSF Package Analysis project identified 'shinhan-limit-scrap' @ 1.0.3 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

1a36e94227053e43949ff8502ae523f557fe032a9278baedabbc61a3e8922ac5

dae6aee79d5386d3525290fdc37160052ab2cfc88cfe444751cf1e0c09122b48

d08f28475b82db9e50e3451766d02611ceada3515c80725fd5cba68ad4de79ca

3d8167f5d54de35da140b0d6bfc89ea32b737db0e10a68b1cbdbd0c975722a88

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 shinhan-limit-scrap (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shinhan-limit-scrap across your stack and pipelines.
If you installed it — respond
shinhan-limit-scrap 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 shinhan-limit-scrap 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 shinhan-limit-scrap 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. shinhan-limit-scrap 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

GHSA-p92h-9qvq-2vq2

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks shinhan-limit-scrap-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