Which versions of dwaiter-company-web are malicious?

The following npm versions of dwaiter-company-web are flagged malicious: 99.9.0. Treat any of these as compromised.

How do I remediate dwaiter-company-web if I installed it?

Remove dwaiter-company-web 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 dwaiter-company-web — how do I know if it already compromised me?

If dwaiter-company-web 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 dwaiter-company-web part of a known attack campaign?

Yes — dwaiter-company-web is associated with the GHSA-rv36-9mrp-x3ch, RLMA-2026-05044 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 dwaiter-company-web 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 dwaiter-company-web (version 99.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dwaiter-company-web across your stack and pipelines.

Malicious package

dwaiter-company-webnpm

dwaiter-company-web is a confirmed malicious npm package (MAL-2026-2601) that executes malicious code on install (malicious version 99.9.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dwaiter-company-web (npm)

MAL-2026-2601

Immediate action

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

npm uninstall dwaiter-company-web

What this malware does

The package dwaiter-company-web 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

1 flagged

99.9.0

Indicators of compromise (SHA-256)

7b1153673ad92ffcdd394be22a3a3aefd3add908f645bfd773c52caab143525b

602a450ab8f9d48b5e7ca03f6e4cf89803a6f1a0e6e35d453c92e59143096577

a1bc16bc223851da9e5aa5c5a822b40e259d4ff52c9b58b1d464892acfde8cab

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

Campaign

GHSA-rv36-9mrp-x3chRLMA-2026-05044

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dwaiter-company-web-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

Explore

All malware advisories How O3 detects malware Vulnerability database