Which versions of @offa/offa-uwk are malicious?

The following npm versions of @offa/offa-uwk are flagged malicious: 999.0.0, 999.0.1. Treat any of these as compromised.

How do I remediate @offa/offa-uwk if I installed it?

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

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

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

Malicious package

@offa/offa-uwknpm

@offa/offa-uwk is a confirmed malicious npm package (MAL-2026-12326) that steals credentials and exfiltrates sensitive data (malicious versions 999.0.0, 999.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @offa/offa-uwk (npm)

MAL-2026-12326

Immediate action

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

npm uninstall @offa/offa-uwk

What this malware does

package.json declares a postinstall hook that runs index.js. On install, index.js collects os.hostname(), os.userInfo().username, process.cwd(), and the entire process.env object, then POSTs the JSON payload via https.request to the hardcoded endpoint https://e6b10849-38dc-4280-a8e3-72ab39cfaf65.webhook.site/collect. Dumping the whole process environment on install ships every environment variable on the installer's machine — commonly containing AWS/GCP/GitHub/npm and other tokens — to an anonymous attacker-controlled webhook. A preinstall hook additionally writes a marker file to the hardcoded absolute path /home/OFFA/flag.

Malicious versions

2 flagged

999.0.0999.0.1

Indicators of compromise (SHA-256)

321b84802e64efd2edf01527613d8d37aeaa63ee37505c59bf48a94f5ec88aed

3a04489d4763fb48f4c5bc4ea7e99802b21a412ba55900ae7bf411070e2a42d8

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

Campaign

IN-MAL-2026-014821IN-MAL-2026-014853

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @offa/offa-uwk-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