Which versions of wml-core are malicious?

The following npm versions of wml-core are flagged malicious: 99.0.1. Treat any of these as compromised.

How do I remediate wml-core if I installed it?

wml-core 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 wml-core — how do I know if it already compromised me?

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

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

Malicious package

wml-corenpm

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

MAL-2026-4731

Immediate action

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

npm uninstall wml-core

What this malware does

[email protected] is a dependency-confusion package targeting an internal wml-* namespace, published with an inflated version (99.0.1) to win npm resolution against an internal package of the same name. The preinstall script poc.js runs automatically on npm install and harvests: hostname, username, OS/platform info, full network configuration (ipconfig /all on Windows or ip a + /etc/resolv.conf on Linux), whoami /all / id output, git remote URLs, the parent project's package.json, CI configuration files (.gitlab-ci.yml, .github/workflows/*, Jenkinsfile, azure-pipelines.yml), and a filtered dump of process.env matching credential-bearing prefixes including TOKEN, AWS, AZURE, NPM, GITHUB, GITLAB, JENKINS, WALMART, WMT, CI_. The collected JSON blob is POSTed to d8a5d9pon5bugoc35cngp9hcregcqyezu.oast.me (an Interactsh out-of-band callback host) over HTTPS, with a DNS callback emitted as a side channel. Any installer outside the intended target scope — including unintended internal builds and any third party who installs this name — has their build environment, CI secrets, and cloud/registry tokens exfiltrated. The package's self-description as 'authorized bug bounty research' does not change installer-side harm: the payload fires unconditionally on any npm install.

Malicious versions

1 flagged

99.0.1

Indicators of compromise (SHA-256)

46afe229d6efe1ef10d025302ed21e5c2c44bdd772c8fbb28d037cb1215c84ba

9bb6cda0457187b67ae8822ebe66fe54310bfbecdd658f7beabab10cc54527a7

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

Campaign

IN-MAL-2026-004689IN-MAL-2026-004691

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks wml-core-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