Which versions of @dransay/secrets are malicious?

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

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

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

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

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

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

Malicious package

@dransay/secretsnpm

Advisory published Oct 8, 2026Updated Oct 12, 2026

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

MAL-2026-17699

Immediate action

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

npm uninstall @dransay/secrets

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 declares a preinstall script that runs beacon.js, which performs a DNS lookup and HTTPS GET to a hardcoded Interactsh collector host (db3klhbi6i9hark1kegg174t38h33b6wt.oast.site) at npm install time. Both the DNS query and the HTTPS request embed the package name, so any machine that resolves and installs this scoped name sends an unsolicited out-of-band callback carrying the installing host's source IP, resolver identity, timing, and the internal package name to a third-party collector. The implausibly high 99.0.0 version against a scoped name is the dependency-confusion shape — the artifact is intended to win resolution against an internal @dransay/secrets and beacon from whichever build environment resolves it, disclosing internal network and build-system identity. No functional library code accompanies the beacon; the package's only on-install effect is the callback.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

aef0f6b36413e45664391c5341f7c30a4501c2cc916add9ba6525bf57e559d51

Detection & response playbook

Backdoor / remote access

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

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

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