Which versions of dransay are malicious?

The following npm versions of dransay are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate dransay if I installed it?

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

If dransay was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dransay part of a known attack campaign?

Yes — dransay is associated with the IN-MAL-2026-021227 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 dransay across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dransay (version 99.0.0).

Malicious package

dransaynpm

Advisory published Oct 8, 2026Updated Oct 12, 2026

dransay is a confirmed malicious npm package (MAL-2026-17700) that opens a backdoor for remote access (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dransay (npm)

MAL-2026-17700

Immediate action

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

npm uninstall dransay

What this malware does

[email protected] is a dependency-confusion probe for an internal unscoped dransay package name, not an identified public package. Its preinstall hook runs on npm install as node beacon.js and sends a DNS lookup and an HTTPS GET to db3klhbi6i9hark1kegg174t38h33b6wt.oast.site, using dransay-unscoped in the request; npm account 0xamino_hunter published it on 2026-10-08.

[email protected] declares a preinstall lifecycle script that runs node beacon.js, which performs a DNS lookup and HTTPS GET against a hardcoded Interactsh (oast.site) collaborator subdomain (db3klhbi6i9hark1kegg174t38h33b6wt.oast.site) on every npm install. The outbound request discloses the installer's source IP, DNS resolver IP, hostname-derived data, and timestamp to a third-party collaborator host unrelated to any first-party publisher. The package name and implausibly high version (99.0.0) are consistent with a dependency-confusion probe targeting an internal package name. The README self-labels the package as a benign dependency-confusion proof-of-concept; the self-label does not change the behavior — install-time, non-consensual outbound network I/O to a researcher-controlled OAST host that collects installer network identity.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

46d06d0ce82913346840f676660d67f9838f48511e58eef793bfe7c52091071f

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for dransay (version 99.0.0).
If you installed it — respond
dransay 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 dransay was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dransay on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021227

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

O3 blocks dransay-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