Which versions of @dransay/logger are malicious?

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

How do I remediate @dransay/logger if I installed it?

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

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

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

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

Malicious package

@dransay/loggernpm

Advisory published Oct 8, 2026Updated Oct 12, 2026

@dransay/logger is a confirmed malicious npm package (MAL-2026-17697) 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/logger (npm)

MAL-2026-17697

Immediate action

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

npm uninstall @dransay/logger

What this malware does

@dransay/[email protected] is a dependency-confusion probe claiming the internal @dransay/* namespace, 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 the package name in the request; npm account 0xamino_hunter published it on 2026-10-08.

The package @dransay/[email protected] ships a preinstall hook (node beacon.js) that fires on npm install. The script performs a DNS lookup and HTTPS GET to the interactsh collaborator host db3klhbi6i9hark1kegg174t38h33b6wt.oast.site, encoding the package name in the subdomain/path. The version number (99.0.0) is implausibly high for a package with no release history, consistent with a dependency-confusion squat intended to win semver resolution against a private internal name. On install, the beacon discloses the installer's source IP, DNS resolver, and timestamp to a third-party host under the scoped name @dransay/logger, confirming successful resolution of this public package in an environment that may have intended to resolve a private @dransay/* package. No further payload is executed in this version, but the install-time callback to an attacker-controlled OAST endpoint is the reconnaissance stage of a dependency-confusion attack.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

5d4cbd17edce3b0c45619c9af869321807357e3dae1af8aa94835d3143185e85

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for @dransay/logger (version 99.0.0).
If you installed it — respond
@dransay/logger 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/logger 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/logger 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-021217

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

O3 blocks @dransay/logger-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