Which versions of @xyuxu/i18never are malicious?

Every published version of @xyuxu/i18never on npm is considered malicious. Remove the package entirely.

How do I remediate @xyuxu/i18never if I installed it?

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

If @xyuxu/i18never 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 @xyuxu/i18never part of a known attack campaign?

Yes — @xyuxu/i18never is associated with the GHSA-jg82-rrfm-828g 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 @xyuxu/i18never 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 @xyuxu/i18never (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @xyuxu/i18never across your stack and pipelines.

Malicious package

@xyuxu/i18nevernpm

Malicious code in @xyuxu/i18never (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192617

Immediate action

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

npm uninstall @xyuxu/i18never

What this malware does

The package @xyuxu/i18never 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

3c5087826460532be47bc7b783c6674322cc348a195d708d058f98f7d73ec22b

1b923f08dbda49245b6cdc13f30d46556f98e438c1788b29597ff1d64446bf54

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

Campaign

GHSA-jg82-rrfm-828g

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @xyuxu/i18never-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