dds-js-idl
This report shows the evidence for dds-js-idl@1.0.1. 2 of 2 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4264 confirms this npm version as malicious.
Advisory
MAL-2026-4264
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in dds-js-idl (npm)
Details
On `npm install`, postinstall.js runs `whoami` via execSync and collects os.hostname(), os.platform(), cwd, and CI/GitHub env vars, then exfiltrates them over HTTPS GET to `lg5ys3jebfzwk366pilidbmah1nsbszh.oastify.com/nasa/dds-js-canary/` and additionally performs a DNS lookup of `${whoami}.lg5ys3jebfzwk366pilidbmah1nsbszh.oastify.com` as a DNS-channel fallback that defeats egress HTTPS filtering. The package self-describes as a `Security research canary — NASA VDP`, but it fires on every install without consent and leaks installer identity and repository/CI context to a third-party Interactsh (oastify.com) collector controlled by the canary operator. Regardless of stated research intent, the structural behavior is install-time host fingerprinting and out-of-band exfiltration.
## Source: ossf-package-analysis (282ab4387de68701d586cdeb6635a576abea042584decbb31640112e9292e83a) The OpenSSF Package Analysis project identified 'dds-js-idl' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to dds-js-idl@1.0.1.
The same advisory and Firewall decision cover 2 recorded versions
1.0.0, 1.0.1
The versions list below shows the verdict for each recorded version.
- Avoid installing dds-js-idl@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.