Which versions of onewin-landing are malicious?

The following npm versions of onewin-landing are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate onewin-landing if I installed it?

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

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

Yes — onewin-landing is associated with the GHSA-6xf2-88r3-x5gr, RLMA-2026-02013 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 onewin-landing 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 onewin-landing (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging onewin-landing across your stack and pipelines.

Malicious package

onewin-landingnpm

Malicious code in onewin-landing (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2652

Immediate action

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

npm uninstall onewin-landing

What this malware does

The package onewin-landing 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.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

af836df2faf0017725ed9fdbcd5457bfca0045b6a8d9cbad8e1ca949f4f06938

2ca8df32d685e891dbfe57504fff8034c293c7ac7892f4f51a8ee93faaf4804d

38fa6b80b5e487a83f8ed1eccfcc9d4bbb5d460deb678e1106aea26439c11f24

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

Campaign

GHSA-6xf2-88r3-x5grRLMA-2026-02013

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks onewin-landing-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