Which versions of yuinpm are malicious?

The following npm versions of yuinpm are flagged malicious: 2026.7.19-2. Treat any of these as compromised.

How do I remediate yuinpm if I installed it?

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

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

Yes — yuinpm is associated with the GHSA-vpgm-qmgp-w4h4, IN-MAL-2026-013308 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 yuinpm 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 yuinpm (version 2026.7.19-2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yuinpm across your stack and pipelines.

Malicious package

yuinpmnpm

yuinpm is a confirmed malicious npm package (MAL-2026-11039) that steals credentials and exfiltrates sensitive data (malicious version 2026.7.19-2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in yuinpm (npm)

MAL-2026-11039

Immediate action

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

npm uninstall yuinpm

What this malware does

Package [email protected] contains 3 files and produced no a static rule matches and no traced-code findings indicating exfiltration, install-time remote code execution, silent relay, credential distribution, self-propagation, or backdoor behavior. The unusual calendar-style version number is a metadata observation only and is not itself a supply-chain threat.

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

2026.7.19-2

Indicators of compromise (SHA-256)

d036e3cc02bd090bae9ff004d7559fd524b963bb47fee0a0a6cd6baf1395c2be

b4f439dbbb74a729ef5c43bdc62f612060dbc9e6a96b825c8305b88dd43b3172

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 yuinpm (version 2026.7.19-2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yuinpm across your stack and pipelines.
If you installed it — respond
yuinpm 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 yuinpm 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 yuinpm 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. yuinpm on npm has been identified as a malicious package (version 2026.7.19-2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vpgm-qmgp-w4h4IN-MAL-2026-013308

References

Credits

Amazon Inspector · finder

Detect & block this

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