Which versions of @sarex-team/translator are malicious?

The following npm versions of @sarex-team/translator are flagged malicious: 9.9.11. Treat any of these as compromised.

How do I remediate @sarex-team/translator if I installed it?

@sarex-team/translator 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 @sarex-team/translator — how do I know if it already compromised me?

If @sarex-team/translator 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 @sarex-team/translator part of a known attack campaign?

Yes — @sarex-team/translator is associated with the IN-MAL-2026-018290 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 @sarex-team/translator 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 @sarex-team/translator (version 9.9.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sarex-team/translator across your stack and pipelines.

Malicious package

@sarex-team/translatornpm

@sarex-team/translator is a confirmed malicious npm package (MAL-2026-14205) that steals credentials and exfiltrates sensitive data (malicious version 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sarex-team/translator (npm)

MAL-2026-14205

Immediate action

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

npm uninstall @sarex-team/translator

What this malware does

The package's install lifecycle script (scripts.install="node index.js") automatically executes on npm install and loads lib/core.js. That module reads os.userInfo().username, os.hostname(), and the basename of process.cwd(), concatenates them with a timestamp as subdomain labels, and issues a dns.resolve4 lookup against oob.sl4x0.xyz — encoding the installer's identity into a DNS query that reaches the attacker's authoritative nameserver. The destination domain, the module names ('os', 'dns', 'process'), and the accessor names ('userInfo', 'hostname', 'cwd') are reconstructed at runtime from char-code arrays in hex-named files (lib/b02e30.js, lib/6ad264.js), concealing the exfiltration path from casual review. The exfil domain sl4x0.xyz matches the package author's contact email ([email protected]), confirming the destination is author-controlled.

Malicious versions

1 flagged

9.9.11

Indicators of compromise (SHA-256)

0bccb8e95706f8ed3fe0408d43f6e043f6db71126f1951dda76bda7dfcc134e6

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

Campaign

IN-MAL-2026-018290

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @sarex-team/translator-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