Which versions of domains-billing-types are malicious?

The following npm versions of domains-billing-types are flagged malicious: 99.91.1. Treat any of these as compromised.

How do I remediate domains-billing-types if I installed it?

domains-billing-types establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed domains-billing-types — how do I know if it already compromised me?

If domains-billing-types 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 domains-billing-types part of a known attack campaign?

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

Malicious package

domains-billing-typesnpm

domains-billing-types is a confirmed malicious npm package (MAL-2026-6980) that opens a backdoor for remote access (malicious version 99.91.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in domains-billing-types (npm)

MAL-2026-6980

Immediate action

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

npm uninstall domains-billing-types

What this malware does

[email protected] executes node index.js from its postinstall lifecycle script. On install, index.js reads os.hostname() and os.userInfo().username and embeds them as subdomain labels in a DNS A-record lookup to <hostname>.<username>.aiwm5lowso4vtjynsoije5q4rvxmlf94.oastify.com (Burp Suite Collaborator, an out-of-band interaction server). The DNS resolution transmits the installer's host and user identity to an attacker-controlled OAST endpoint at install time, without consent. The package has anonymous authorship, an empty description ("Billing!"), and no real functionality — the name and shape are consistent with a dependency-confusion probe against an internal package namespace, with the DNS beacon confirming any successful resolution.

The OpenSSF Package Analysis project identified 'domains-billing-types' @ 99.91.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.91.1

Indicators of compromise (SHA-256)

11558e73bc928dd5dadd7ba70e9256e5458e6d829c63a577a31740d2f6c553e1

4860726efc056e319a24e46ac4e179809cc294267679a9b8122c5205b49369f1

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for domains-billing-types (version 99.91.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging domains-billing-types across your stack and pipelines.
If you installed it — respond
domains-billing-types establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If domains-billing-types 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 domains-billing-types 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. domains-billing-types on npm has been identified as a malicious package (version 99.91.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009246

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks domains-billing-types-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database