Which versions of shenxun162938 are malicious?

The following npm versions of shenxun162938 are flagged malicious: 1.0.9. Treat any of these as compromised.

How do I remediate shenxun162938 if I installed it?

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

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

Yes — shenxun162938 is associated with the GHSA-c8v3-pvm5-9xx2 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 shenxun162938 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 shenxun162938 (version 1.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shenxun162938 across your stack and pipelines.

Malicious package

shenxun162938npm

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

Malicious code in shenxun162938 (npm)

MAL-2026-2256

Immediate action

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

npm uninstall shenxun162938

What this malware does

The package shenxun162938 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.

The OpenSSF Package Analysis project identified 'shenxun162938' @ 1.0.9 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.9

Indicators of compromise (SHA-256)

e3f16a189535f0c564b715a46ab33b16f6109cef759130464d82239bac12775d

19e684dce319a00214edebc8d8838e4402d88146cff78f1eadf297cad0e3a2ab

0dda575a13831bf3df894664e6e2a6a107e33099c3fba68937d4ff1dde1c8317

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for shenxun162938 (version 1.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shenxun162938 across your stack and pipelines.
If you installed it — respond
Remove shenxun162938 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 shenxun162938 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 shenxun162938 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. shenxun162938 on npm has been identified as a malicious package (version 1.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c8v3-pvm5-9xx2

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks shenxun162938-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