Which versions of typst-resume-cli are malicious?

The following npm versions of typst-resume-cli are flagged malicious: 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate typst-resume-cli if I installed it?

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

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

Yes — typst-resume-cli is associated with the IN-MAL-2026-016363, IN-MAL-2026-016361 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 typst-resume-cli 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 typst-resume-cli (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging typst-resume-cli across your stack and pipelines.

Malicious package

typst-resume-clinpm

typst-resume-cli is a confirmed malicious npm package (MAL-2026-13425) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in typst-resume-cli (npm)

MAL-2026-13425

Immediate action

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

npm uninstall typst-resume-cli

What this malware does

index.js loads https, http, and child_process at the top of the module and sends host/environment data to a hardcoded AWS Lambda URL at https://oo7fsr4cy32q42bzkpgwhy7asu0hzaod.lambda-url.us-east-1.on.aws. The code reads process.env and branches on process.platform before issuing an https.request to that endpoint. The destination is an attacker-controlled serverless URL unrelated to a Typst or resume tooling publisher, and the collected data (environment variables and host attributes) is credential-grade content leaving the installer's machine.

Malicious versions

2 flagged

1.0.21.0.3

Indicators of compromise (SHA-256)

104d03639d9a9d48d03641fef83163391bb1540c8a01c56287bcaf8ca45ad01c

cf49520847fad0a4e5351cf63bd0e5bf3e13bf0a46478ac528318fd4e07156bf

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

Campaign

IN-MAL-2026-016363IN-MAL-2026-016361

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks typst-resume-cli-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